Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d88e62be3fb4d4d1c333da0c6ca2143e2e4354702b75ba2cddaecd1959bdb04

Tx prefix hash: d3423fcb10cbdbc1ceb4f731df39b3c5c232e251d2bd554169257d2eec99532c
Tx public key: f1e9e53e303ccbdbf697e91b837006279ce74f12f8b5fefb7a3ae14c1b3a4c4a
Timestamp: 1710879724 Timestamp [UCT]: 2024-03-19 20:22:04 Age [y:d:h:m:s]: 01:008:20:55:27
Block: 981960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267302 RingCT/type: yes/0
Extra: 01f1e9e53e303ccbdbf697e91b837006279ce74f12f8b5fefb7a3ae14c1b3a4c4a02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fb16e757acac5c9b09933c2c4355223e882dce6d1099a976330cc54657bc8d5 0.600000000000 1442063 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": 981970, "vin": [ { "gen": { "height": 981960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fb16e757acac5c9b09933c2c4355223e882dce6d1099a976330cc54657bc8d5" } } ], "extra": [ 1, 241, 233, 229, 62, 48, 60, 203, 219, 246, 151, 233, 27, 131, 112, 6, 39, 156, 231, 79, 18, 248, 181, 254, 251, 122, 58, 225, 76, 27, 58, 76, 74, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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