Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d23731e1ea107dd1671120f2f9a1232e0b242c90bdf60f5e3922716798d9db5

Tx prefix hash: 94403f34ebf435aed0e294e1652c2e703a176e9a93811325661e104e5d3661fb
Tx public key: fef65de8a25e76b6b5b4e05eac4fcf6a075afd0b4b54c23e0eb8888f832f89ac
Timestamp: 1716407665 Timestamp [UCT]: 2024-05-22 19:54:25 Age [y:d:h:m:s]: 00:298:07:01:58
Block: 1027774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213201 RingCT/type: yes/0
Extra: 01fef65de8a25e76b6b5b4e05eac4fcf6a075afd0b4b54c23e0eb8888f832f89ac02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a23d798e312c7971157585e47fdfb741ab1e19157151795570ffc8e85786f8c 0.600000000000 1495575 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": 1027784, "vin": [ { "gen": { "height": 1027774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a23d798e312c7971157585e47fdfb741ab1e19157151795570ffc8e85786f8c" } } ], "extra": [ 1, 254, 246, 93, 232, 162, 94, 118, 182, 181, 180, 224, 94, 172, 79, 207, 106, 7, 90, 253, 11, 75, 84, 194, 62, 14, 184, 136, 143, 131, 47, 137, 172, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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