Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af60e072011d36194f10c951e4a5a96f9094c7c3bd854e51c3306c6d81bc65a5

Tx prefix hash: bf526475678e6825d8d4802fb1448f1072044c5065c54ed439d5ae4252ff0aa7
Tx public key: 22e9963cfa17e6fd1309ebbb39c1d65d477e4c192789b77defa3a473a3f41921
Timestamp: 1716873547 Timestamp [UCT]: 2024-05-28 05:19:07 Age [y:d:h:m:s]: 00:300:18:38:59
Block: 1031646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214943 RingCT/type: yes/0
Extra: 0122e9963cfa17e6fd1309ebbb39c1d65d477e4c192789b77defa3a473a3f419210211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef77ff9d8916199c6d7d7847cdb74ee7c7cff64bb068a6094ee2e2be46722c4a 0.600000000000 1500095 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": 1031656, "vin": [ { "gen": { "height": 1031646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef77ff9d8916199c6d7d7847cdb74ee7c7cff64bb068a6094ee2e2be46722c4a" } } ], "extra": [ 1, 34, 233, 150, 60, 250, 23, 230, 253, 19, 9, 235, 187, 57, 193, 214, 93, 71, 126, 76, 25, 39, 137, 183, 125, 239, 163, 164, 115, 163, 244, 25, 33, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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