Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17bbb0bbe3d567092a85e090f42eda254ac43372d50ccfb8896c1c20a354faaf

Tx prefix hash: fb1441ccd2ad1444936fea42aab522dfeb0839974ff9b67076ae78105cc78a14
Tx public key: 94c251c8e62b0d743d7498ca08b2cbbcf7ee0691d4ef7c054a0e07db3b926f76
Timestamp: 1722781458 Timestamp [UCT]: 2024-08-04 14:24:18 Age [y:d:h:m:s]: 00:246:00:51:40
Block: 1080607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175743 RingCT/type: yes/0
Extra: 0194c251c8e62b0d743d7498ca08b2cbbcf7ee0691d4ef7c054a0e07db3b926f76021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6bd7cd70cae6579565b8f1192ad41359a3e32d3f5a94a583dfa15c77446e534 0.600000000000 1554040 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": 1080617, "vin": [ { "gen": { "height": 1080607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6bd7cd70cae6579565b8f1192ad41359a3e32d3f5a94a583dfa15c77446e534" } } ], "extra": [ 1, 148, 194, 81, 200, 230, 43, 13, 116, 61, 116, 152, 202, 8, 178, 203, 188, 247, 238, 6, 145, 212, 239, 124, 5, 74, 14, 7, 219, 59, 146, 111, 118, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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