Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f393512ad3ef78b9107582ed4689d8e75f58d57a5d74ab06a7c683acb2abb9d6

Tx prefix hash: 31240c79dc307409f269c44ad016546e2d5e91cffea7368707a18b326c167d59
Tx public key: f00ea3e48892a32502b46407c93cbe5f59d6f703017a12f6191a4a1ae8998250
Timestamp: 1722572870 Timestamp [UCT]: 2024-08-02 04:27:50 Age [y:d:h:m:s]: 00:250:03:47:20
Block: 1078882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178691 RingCT/type: yes/0
Extra: 01f00ea3e48892a32502b46407c93cbe5f59d6f703017a12f6191a4a1ae899825002110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72c8f330865d4f4764e6c3081d2402399315e2f9045df72c91864b3b98969ccc 0.600000000000 1551601 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": 1078892, "vin": [ { "gen": { "height": 1078882 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72c8f330865d4f4764e6c3081d2402399315e2f9045df72c91864b3b98969ccc" } } ], "extra": [ 1, 240, 14, 163, 228, 136, 146, 163, 37, 2, 180, 100, 7, 201, 60, 190, 95, 89, 214, 247, 3, 1, 122, 18, 246, 25, 26, 74, 26, 232, 153, 130, 80, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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