Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c02fa4eab12f8a17450a24e38ddb3a847a5244f21318ddf5e6d7fa3f2e0cc21

Tx prefix hash: 644bb6b8b986dbcfd53d6916194b561e7687d58c8f4981b7c56c95289dc10d83
Tx public key: 6aa478d6f646672d19badb891fd1b1d2ceacac76431aa177e7b1f5254bc34b2f
Timestamp: 1580719382 Timestamp [UCT]: 2020-02-03 08:43:02 Age [y:d:h:m:s]: 04:324:22:27:29
Block: 57838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123469 RingCT/type: yes/0
Extra: 016aa478d6f646672d19badb891fd1b1d2ceacac76431aa177e7b1f5254bc34b2f02110000004dd81c26c0000000000000000000

1 output(s) for total of 394.783977046000 dcy

stealth address amount amount idx
00: c6555f2d84dad2d4fd7213f589a3faba74e891cb09692e7e4ee4b32f7c1d6b55 394.783977046000 106930 of 0

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": 57848, "vin": [ { "gen": { "height": 57838 } } ], "vout": [ { "amount": 394783977046, "target": { "key": "c6555f2d84dad2d4fd7213f589a3faba74e891cb09692e7e4ee4b32f7c1d6b55" } } ], "extra": [ 1, 106, 164, 120, 214, 246, 70, 103, 45, 25, 186, 219, 137, 31, 209, 177, 210, 206, 172, 172, 118, 67, 26, 161, 119, 231, 177, 245, 37, 75, 195, 75, 47, 2, 17, 0, 0, 0, 77, 216, 28, 38, 192, 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