Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c5dc5140a3da9d52a676a03f21a800138ad1a9fe6de624e5a7b583d844da28f

Tx prefix hash: b02fdb5b2ed6632a802fb814b4f896dfd8eaa3ba33bb4ddda02b8c4d827875d9
Tx public key: 73c8b09debe84b01e066b88333cf861f3b76aee5caf86c3092eb556567f69d96
Timestamp: 1736613866 Timestamp [UCT]: 2025-01-11 16:44:26 Age [y:d:h:m:s]: 00:343:07:35:59
Block: 1195147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242936 RingCT/type: yes/0
Extra: 0173c8b09debe84b01e066b88333cf861f3b76aee5caf86c3092eb556567f69d9602110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c2102b0a4c61130056f95b9ce3a5a6c499160d1d8c5fd694d729cda533a13dc 0.600000000000 1681736 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": 1195157, "vin": [ { "gen": { "height": 1195147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c2102b0a4c61130056f95b9ce3a5a6c499160d1d8c5fd694d729cda533a13dc" } } ], "extra": [ 1, 115, 200, 176, 157, 235, 232, 75, 1, 224, 102, 184, 131, 51, 207, 134, 31, 59, 118, 174, 229, 202, 248, 108, 48, 146, 235, 85, 101, 103, 246, 157, 150, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 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