Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: a381d58884131a50d1734e0e3452a76e75af88e04cfcf16263284ce9d6a65df4

Tx prefix hash: 6047e79d026842148374e29666ea21c51328ee3e45f4487b71a05a7b796ceb5c
Tx public key: f4a0c358e61935019e8343f600ddff5898add4da4c5615d2c6ccaaf82d62f60c
Timestamp: 1713118060 Timestamp [UCT]: 2024-04-14 18:07:40 Age [y:d:h:m:s]: 00:224:01:12:17
Block: 1000480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160411 RingCT/type: yes/0
Extra: 01f4a0c358e61935019e8343f600ddff5898add4da4c5615d2c6ccaaf82d62f60c0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37803e509b1e53e09e016091dacd37cb8fab3a0e7924a263ea823ce0d4e05372 0.600000000000 1460978 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1000490, "vin": [ { "gen": { "height": 1000480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37803e509b1e53e09e016091dacd37cb8fab3a0e7924a263ea823ce0d4e05372" } } ], "extra": [ 1, 244, 160, 195, 88, 230, 25, 53, 1, 158, 131, 67, 246, 0, 221, 255, 88, 152, 173, 212, 218, 76, 86, 21, 210, 198, 204, 170, 248, 45, 98, 246, 12, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8