Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33cd14176e95d05d37e5b193027a98bb31576bf07a3d917c6725e7ce35a5b349

Tx prefix hash: 81fbfdc2653f8adc14f01463fc6260eb8a1324eee3d87260fd7612121be570d9
Tx public key: 3c5ee2c311f7f7de9f7f25a783f62f3cb744c835fc4c81510b811cf7cbac8ad6
Timestamp: 1709485991 Timestamp [UCT]: 2024-03-03 17:13:11 Age [y:d:h:m:s]: 01:102:11:58:34
Block: 970394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334223 RingCT/type: yes/0
Extra: 013c5ee2c311f7f7de9f7f25a783f62f3cb744c835fc4c81510b811cf7cbac8ad60211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5dcaa9fe7a83dedbb367305cb46addbaa63ac1438c7af2946576dde9b55ada5b 0.600000000000 1430247 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": 970404, "vin": [ { "gen": { "height": 970394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5dcaa9fe7a83dedbb367305cb46addbaa63ac1438c7af2946576dde9b55ada5b" } } ], "extra": [ 1, 60, 94, 226, 195, 17, 247, 247, 222, 159, 127, 37, 167, 131, 246, 47, 60, 183, 68, 200, 53, 252, 76, 129, 81, 11, 129, 28, 247, 203, 172, 138, 214, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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