Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31211e938d304d02cff4b066f06bfcfe321e5c4d390bd8b59d59b3d59ef2aded

Tx prefix hash: 2eac15529d6f55dd7a79cb7eec997079390decb3310f159d972f4fb7172bb196
Tx public key: 823271b0db4ace5973488cbc1cc88db3f6b9e203dc8dedd6dcb15bea72ff6b14
Timestamp: 1754761303 Timestamp [UCT]: 2025-08-09 17:41:43 Age [y:d:h:m:s]: 00:104:08:21:44
Block: 1343622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73728 RingCT/type: yes/0
Extra: 01823271b0db4ace5973488cbc1cc88db3f6b9e203dc8dedd6dcb15bea72ff6b14021100000008ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35e5091243c5231b649042b7b6ad491f80b1d6c412a83c4969d1b7746bd8583d 0.600000000000 1831463 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": 1343632, "vin": [ { "gen": { "height": 1343622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35e5091243c5231b649042b7b6ad491f80b1d6c412a83c4969d1b7746bd8583d" } } ], "extra": [ 1, 130, 50, 113, 176, 219, 74, 206, 89, 115, 72, 140, 188, 28, 200, 141, 179, 246, 185, 226, 3, 220, 141, 237, 214, 220, 177, 91, 234, 114, 255, 107, 20, 2, 17, 0, 0, 0, 8, 173, 121, 72, 208, 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