Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 594b692181b815af420a473e4ff2dc6346dc8a6daab3ab27e061b906a15e8ae6

Tx prefix hash: c8c3d5180bfa2be81d9605071dcb4584197effbc593e4f1033a3535482af649e
Tx public key: 156030e1448fe34b3ba38c190d2cbb901e688844e293bccf48f0e4e3a0625a9a
Timestamp: 1717116834 Timestamp [UCT]: 2024-05-31 00:53:54 Age [y:d:h:m:s]: 00:359:10:41:53
Block: 1033650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256936 RingCT/type: yes/0
Extra: 01156030e1448fe34b3ba38c190d2cbb901e688844e293bccf48f0e4e3a0625a9a021100000002679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6e28f5344c0056e6ac18aad0f7558399f296d47c0dc0e7ca41f7317f460e86a 0.600000000000 1502121 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": 1033660, "vin": [ { "gen": { "height": 1033650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6e28f5344c0056e6ac18aad0f7558399f296d47c0dc0e7ca41f7317f460e86a" } } ], "extra": [ 1, 21, 96, 48, 225, 68, 143, 227, 75, 59, 163, 140, 25, 13, 44, 187, 144, 30, 104, 136, 68, 226, 147, 188, 207, 72, 240, 228, 227, 160, 98, 90, 154, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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