Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d56c802f964b5640e0ece66158891c7e2db0f7dbb9476bed6d7fa3e04fbdefee

Tx prefix hash: 1a2991845979ae11e95cdb7a190c9ca21aef6c86009fae248ea7d942cc954f5b
Tx public key: 989dd28e4be509cfa5c54dd71d4374c2eabd5dac77b14868a24e86f6c852a5e9
Timestamp: 1708313443 Timestamp [UCT]: 2024-02-19 03:30:43 Age [y:d:h:m:s]: 00:286:05:50:13
Block: 960668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204944 RingCT/type: yes/0
Extra: 01989dd28e4be509cfa5c54dd71d4374c2eabd5dac77b14868a24e86f6c852a5e902110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ddf63e74d36fc56bf75dfce9ab4aaf9d8c22726cdd4c311bc82e5a579f6c1d2 0.600000000000 1420255 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": 960678, "vin": [ { "gen": { "height": 960668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ddf63e74d36fc56bf75dfce9ab4aaf9d8c22726cdd4c311bc82e5a579f6c1d2" } } ], "extra": [ 1, 152, 157, 210, 142, 75, 229, 9, 207, 165, 197, 77, 215, 29, 67, 116, 194, 234, 189, 93, 172, 119, 177, 72, 104, 162, 78, 134, 246, 200, 82, 165, 233, 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