Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c8d425ef9641e97c8a5f971c0c0d36accc46b29e30384f47364ee41947dcd11

Tx prefix hash: d6075035b3cc1ec8b5368b351f8340cf4e80fdac5cf9f9dfd15afc5e4e4a1047
Tx public key: 3b5d0c6e76d3fe11e0e21527843629461d5f83770fa61e7708ed82ad92d5289a
Timestamp: 1710830284 Timestamp [UCT]: 2024-03-19 06:38:04 Age [y:d:h:m:s]: 01:234:10:46:17
Block: 981554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426238 RingCT/type: yes/0
Extra: 013b5d0c6e76d3fe11e0e21527843629461d5f83770fa61e7708ed82ad92d5289a0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a61373701d671401756bee271dd1388b91e72294b8ea9eb7e21145b7af00552 0.600000000000 1441651 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": 981564, "vin": [ { "gen": { "height": 981554 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a61373701d671401756bee271dd1388b91e72294b8ea9eb7e21145b7af00552" } } ], "extra": [ 1, 59, 93, 12, 110, 118, 211, 254, 17, 224, 226, 21, 39, 132, 54, 41, 70, 29, 95, 131, 119, 15, 166, 30, 119, 8, 237, 130, 173, 146, 213, 40, 154, 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