Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e66b7c2892edbf662c940a45974073c98ec0e2be7bf89332a4554e52ccd2736

Tx prefix hash: 9ce4aec7c0390fff94871c7716c47c1e85f8fd9bdda9dbdf452018ddce92c683
Tx public key: 18eaf2f465e5171a738c313d369290c1f5db763fb953a6ce67a2e3229a9b4df2
Timestamp: 1700830002 Timestamp [UCT]: 2023-11-24 12:46:42 Age [y:d:h:m:s]: 01:137:23:56:29
Block: 898624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359798 RingCT/type: yes/0
Extra: 0118eaf2f465e5171a738c313d369290c1f5db763fb953a6ce67a2e3229a9b4df202110000000133af99f4000000000000000000

1 output(s) for total of 0.646376616000 dcy

stealth address amount amount idx
00: 73d963347308993d0509794438bbe93f990bc7e13d775735b3b3c7847a685a5b 0.646376616000 1355047 of 0

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": 898634, "vin": [ { "gen": { "height": 898624 } } ], "vout": [ { "amount": 646376616, "target": { "key": "73d963347308993d0509794438bbe93f990bc7e13d775735b3b3c7847a685a5b" } } ], "extra": [ 1, 24, 234, 242, 244, 101, 229, 23, 26, 115, 140, 49, 61, 54, 146, 144, 193, 245, 219, 118, 63, 185, 83, 166, 206, 103, 162, 227, 34, 154, 155, 77, 242, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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