Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a4616da0c06ae0605c329af04833e0263ca79f7fd3338a0f03110e05cf5de56

Tx prefix hash: 3cb42f4e731e8658c66622d918ca52c66a3ff7e6905f5c36cddf01b9b8ecc880
Tx public key: 3fce3ebd9722d617a05a9295c93fde1936af919ffbf11599613f6deaf12359e3
Timestamp: 1712642753 Timestamp [UCT]: 2024-04-09 06:05:53 Age [y:d:h:m:s]: 00:323:04:49:19
Block: 996534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231067 RingCT/type: yes/0
Extra: 013fce3ebd9722d617a05a9295c93fde1936af919ffbf11599613f6deaf12359e302110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4dce7a40935f82f8f913321177f0c5ee0e11956f459f8f4cdcb3045321f3f6f 0.600000000000 1456954 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": 996544, "vin": [ { "gen": { "height": 996534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4dce7a40935f82f8f913321177f0c5ee0e11956f459f8f4cdcb3045321f3f6f" } } ], "extra": [ 1, 63, 206, 62, 189, 151, 34, 214, 23, 160, 90, 146, 149, 201, 63, 222, 25, 54, 175, 145, 159, 251, 241, 21, 153, 97, 63, 109, 234, 241, 35, 89, 227, 2, 17, 0, 0, 0, 3, 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