Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcd2625fdff626b332b5b65d4d9d6b2b2d2f313192071ff7a8baa454f1ecef12

Tx prefix hash: 72d48804201d87d4bee6fc21ac6ea85043da7a0a33117b670a2143238f94fd39
Tx public key: 0b10b6c6e004639add5109561401858b9f9cfb8416cec1cb919d5f35deccbb15
Timestamp: 1713090505 Timestamp [UCT]: 2024-04-14 10:28:25 Age [y:d:h:m:s]: 00:215:02:22:20
Block: 1000256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153996 RingCT/type: yes/0
Extra: 010b10b6c6e004639add5109561401858b9f9cfb8416cec1cb919d5f35deccbb150211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b686d6d5555499a1b2ef217ddb924c9041e205e34c6f96b10ce0ee456779837 0.600000000000 1460752 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": 1000266, "vin": [ { "gen": { "height": 1000256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b686d6d5555499a1b2ef217ddb924c9041e205e34c6f96b10ce0ee456779837" } } ], "extra": [ 1, 11, 16, 182, 198, 224, 4, 99, 154, 221, 81, 9, 86, 20, 1, 133, 139, 159, 156, 251, 132, 22, 206, 193, 203, 145, 157, 95, 53, 222, 204, 187, 21, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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