Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a10d52aa0047df7c3a681e23511784ee7d69847af9b74675817bf10173467e46

Tx prefix hash: 1e400f999655e377332766911038f294b33df2627942d0765ef93af0a419782c
Tx public key: 01ff95ed91e0310ddb7dd5af67b3c4ff0cda0e84c9981c3eb17e09f8709cb3b4
Timestamp: 1704494566 Timestamp [UCT]: 2024-01-05 22:42:46 Age [y:d:h:m:s]: 01:313:01:14:53
Block: 928995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482582 RingCT/type: yes/0
Extra: 0101ff95ed91e0310ddb7dd5af67b3c4ff0cda0e84c9981c3eb17e09f8709cb3b40211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7b6a8357fd3d705f2a8a7139a26bf67b757b9e8fdcba96b9038bdc7eb695670 0.600000000000 1386861 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": 929005, "vin": [ { "gen": { "height": 928995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7b6a8357fd3d705f2a8a7139a26bf67b757b9e8fdcba96b9038bdc7eb695670" } } ], "extra": [ 1, 1, 255, 149, 237, 145, 224, 49, 13, 219, 125, 213, 175, 103, 179, 196, 255, 12, 218, 14, 132, 201, 152, 28, 62, 177, 126, 9, 248, 112, 156, 179, 180, 2, 17, 0, 0, 0, 4, 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