Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 062c9484795a25ed069e8efee94183ba1745eca61aae7278bc544140b5d6aff1

Tx prefix hash: 6b201a721644e63d1d8877c14f6db45c7c3afe509146e628de37acd5b10abefd
Tx public key: ae77ffbbc0cd2ae8a98f26f49c333ebbf27c983100c8f64aeec8c7520d0fdee2
Timestamp: 1704063557 Timestamp [UCT]: 2023-12-31 22:59:17 Age [y:d:h:m:s]: 01:129:02:41:04
Block: 925427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353403 RingCT/type: yes/0
Extra: 01ae77ffbbc0cd2ae8a98f26f49c333ebbf27c983100c8f64aeec8c7520d0fdee202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04a7a5377bf3032afeeb8970d35534e70a54c5af5984368bda073e6e471267ad 0.600000000000 1383189 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": 925437, "vin": [ { "gen": { "height": 925427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04a7a5377bf3032afeeb8970d35534e70a54c5af5984368bda073e6e471267ad" } } ], "extra": [ 1, 174, 119, 255, 187, 192, 205, 42, 232, 169, 143, 38, 244, 156, 51, 62, 187, 242, 124, 152, 49, 0, 200, 246, 74, 238, 200, 199, 82, 13, 15, 222, 226, 2, 17, 0, 0, 0, 2, 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