Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 979f169659f579d6b234172ef3e854e6d38af59e1335356af61437791ecd24e7

Tx prefix hash: 135008cd0cfd37d1ba61df5e482a8c5c0b9cdf00192617770e2a05a5ecdd80cf
Tx public key: d6431dcdbf195a2b4fb5e0bd69d95a58a35a05c876997309b06a1fb8acfa1b4a
Timestamp: 1736096561 Timestamp [UCT]: 2025-01-05 17:02:41 Age [y:d:h:m:s]: 00:079:21:52:20
Block: 1190880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56860 RingCT/type: yes/0
Extra: 01d6431dcdbf195a2b4fb5e0bd69d95a58a35a05c876997309b06a1fb8acfa1b4a021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6986314cea5d54817e624a2addfec38857dddafb004b903682b3d20148b7cba3 0.600000000000 1677403 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": 1190890, "vin": [ { "gen": { "height": 1190880 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6986314cea5d54817e624a2addfec38857dddafb004b903682b3d20148b7cba3" } } ], "extra": [ 1, 214, 67, 29, 205, 191, 25, 90, 43, 79, 181, 224, 189, 105, 217, 90, 88, 163, 90, 5, 200, 118, 153, 115, 9, 176, 106, 31, 184, 172, 250, 27, 74, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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