Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbb606d5b2c94844e343df86de847289d990b95fdf5eb8ebe5a6921d479c27f0

Tx prefix hash: 7544e04e310a39d87e2abde69a6e3b4db37cf8d85616801c578edd29e7ca93c8
Tx public key: 100e014e1956a6da7f8c61050bf82f0d25e6cd9cbcb696392404f3bf4474bab9
Timestamp: 1733808277 Timestamp [UCT]: 2024-12-10 05:24:37 Age [y:d:h:m:s]: 00:100:23:18:48
Block: 1171937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71961 RingCT/type: yes/0
Extra: 01100e014e1956a6da7f8c61050bf82f0d25e6cd9cbcb696392404f3bf4474bab9021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 315efd6bef5b76178d9faf6d2b3e0d964d9d4919be6fec12e0c091fa43054f0b 0.600000000000 1657762 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": 1171947, "vin": [ { "gen": { "height": 1171937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "315efd6bef5b76178d9faf6d2b3e0d964d9d4919be6fec12e0c091fa43054f0b" } } ], "extra": [ 1, 16, 14, 1, 78, 25, 86, 166, 218, 127, 140, 97, 5, 11, 248, 47, 13, 37, 230, 205, 156, 188, 182, 150, 57, 36, 4, 243, 191, 68, 116, 186, 185, 2, 17, 0, 0, 0, 3, 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