Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e2d13e16f6129a1e0653522564c79b23c851dfd1c9629d15dff06f196a93274

Tx prefix hash: 171552e93388623cf7e6ada985a976970f8dd6f2749e04c3d091ef949d23cec8
Tx public key: 389cffb79a4ad9b902038c4f601bd46d1b0a7c22c17975201697a3028fb237e7
Timestamp: 1733876432 Timestamp [UCT]: 2024-12-11 00:20:32 Age [y:d:h:m:s]: 00:101:18:33:45
Block: 1172493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72531 RingCT/type: yes/0
Extra: 01389cffb79a4ad9b902038c4f601bd46d1b0a7c22c17975201697a3028fb237e70211000000026e963a0b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61f52d088195525e76b3831a71d2da2298989a26b3b345e185797c140938c92e 0.600000000000 1658394 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": 1172503, "vin": [ { "gen": { "height": 1172493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61f52d088195525e76b3831a71d2da2298989a26b3b345e185797c140938c92e" } } ], "extra": [ 1, 56, 156, 255, 183, 154, 74, 217, 185, 2, 3, 140, 79, 96, 27, 212, 109, 27, 10, 124, 34, 193, 121, 117, 32, 22, 151, 163, 2, 143, 178, 55, 231, 2, 17, 0, 0, 0, 2, 110, 150, 58, 11, 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