Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbda0830952ec6d03bd93cdddf11fbb88e33f2b549c7dbd9472a789e128355e3

Tx prefix hash: c941e18057764b48dfc505c9cc514e53e2a61d289539429872496874ffe2dd78
Tx public key: 9f2c27435a9582fa2c0a9b8406cb7251e33486e1e81a8cf75bf28fc85df1c6b1
Timestamp: 1736027718 Timestamp [UCT]: 2025-01-04 21:55:18 Age [y:d:h:m:s]: 00:092:23:33:19
Block: 1190304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66219 RingCT/type: yes/0
Extra: 019f2c27435a9582fa2c0a9b8406cb7251e33486e1e81a8cf75bf28fc85df1c6b10211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 575936f832902ad5d66d2b26ee46a896d5a7ea5c77245506a52628bd750b24ce 0.600000000000 1676819 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": 1190314, "vin": [ { "gen": { "height": 1190304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "575936f832902ad5d66d2b26ee46a896d5a7ea5c77245506a52628bd750b24ce" } } ], "extra": [ 1, 159, 44, 39, 67, 90, 149, 130, 250, 44, 10, 155, 132, 6, 203, 114, 81, 227, 52, 134, 225, 232, 26, 140, 247, 91, 242, 143, 200, 93, 241, 198, 177, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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