Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fac5dbb37a9d2d7ab63867a2c56ef3a66a77bed7f808c517832bd0be39a8805a

Tx prefix hash: e515727c983b9608a6205547ab857d31c2a223e860dc856f5fae6e31a8e2a79e
Tx public key: 1c01f2d496a2b5a358cc6c9d1b74f7e65792b16b994ccfdc7298487b22e0146c
Timestamp: 1730660175 Timestamp [UCT]: 2024-11-03 18:56:15 Age [y:d:h:m:s]: 01:047:12:43:37
Block: 1145845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292453 RingCT/type: yes/0
Extra: 011c01f2d496a2b5a358cc6c9d1b74f7e65792b16b994ccfdc7298487b22e0146c021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bef97d11ade01b3eba3515d63667e3d1f131792e46528212e2eb5dc613325af4 0.600000000000 1630370 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": 1145855, "vin": [ { "gen": { "height": 1145845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bef97d11ade01b3eba3515d63667e3d1f131792e46528212e2eb5dc613325af4" } } ], "extra": [ 1, 28, 1, 242, 212, 150, 162, 181, 163, 88, 204, 108, 157, 27, 116, 247, 230, 87, 146, 177, 107, 153, 76, 207, 220, 114, 152, 72, 123, 34, 224, 20, 108, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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