Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ad5d2462d9efb62fd7a4af0c5506f881429cb293b7aa85ab60a0b0c2ba4fffd

Tx prefix hash: 4c883b492cee9ca5e77982b709775201919503c739cc7e6fdd513838fae2ad0e
Tx public key: 4c7db5d228aaa3f868ed4ed5343bcbe53670645440f75a578b5e4e67e2645560
Timestamp: 1722493415 Timestamp [UCT]: 2024-08-01 06:23:35 Age [y:d:h:m:s]: 00:320:01:20:24
Block: 1078224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228581 RingCT/type: yes/0
Extra: 014c7db5d228aaa3f868ed4ed5343bcbe53670645440f75a578b5e4e67e264556002110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b227c831ccc1c9b6a92dcd799dad988aa7f5a6588f28cfa86e6ba72b0cf6f7a2 0.600000000000 1550797 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": 1078234, "vin": [ { "gen": { "height": 1078224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b227c831ccc1c9b6a92dcd799dad988aa7f5a6588f28cfa86e6ba72b0cf6f7a2" } } ], "extra": [ 1, 76, 125, 181, 210, 40, 170, 163, 248, 104, 237, 78, 213, 52, 59, 203, 229, 54, 112, 100, 84, 64, 247, 90, 87, 139, 94, 78, 103, 226, 100, 85, 96, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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