Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 802d4b7a10cc9c036d98d1532964ea6b44f31bffdd638ec2076a9abd07b1f16f

Tx prefix hash: 7aaf456bddded333b099960f6cc241346272ef1eb369607245dc75c6828175cf
Tx public key: d5aa4035560df8caba4e69e32d5bd56e77104cd77b39a7dbfe182eef127a277d
Timestamp: 1704948756 Timestamp [UCT]: 2024-01-11 04:52:36 Age [y:d:h:m:s]: 01:000:08:26:30
Block: 932745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261586 RingCT/type: yes/0
Extra: 01d5aa4035560df8caba4e69e32d5bd56e77104cd77b39a7dbfe182eef127a277d02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3ea0cdd643ac4537a66dc0f2d82a179f75cc380dfbba0f08184eaef0ae6a4ac 0.600000000000 1390685 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": 932755, "vin": [ { "gen": { "height": 932745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3ea0cdd643ac4537a66dc0f2d82a179f75cc380dfbba0f08184eaef0ae6a4ac" } } ], "extra": [ 1, 213, 170, 64, 53, 86, 13, 248, 202, 186, 78, 105, 227, 45, 91, 213, 110, 119, 16, 76, 215, 123, 57, 167, 219, 254, 24, 46, 239, 18, 122, 39, 125, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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