Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b56cff6ad626a6adfca2bd3a4ed27b7b480bcdea447508c9123f592a3818d77

Tx prefix hash: 2567db9753cf065174af87eb671ea4c08d5cdccdc6485d3a211144df6131e35b
Tx public key: 923f5bb2d4d4f6eeb8e5fd3ed984af1646bd5f6e3c84a57cc10f3b5e38b479cc
Timestamp: 1703181184 Timestamp [UCT]: 2023-12-21 17:53:04 Age [y:d:h:m:s]: 01:143:19:20:09
Block: 918114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363922 RingCT/type: yes/0
Extra: 01923f5bb2d4d4f6eeb8e5fd3ed984af1646bd5f6e3c84a57cc10f3b5e38b479cc0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8866cd6ef23e332e75a2cb0b15f132f8520a2971eccf0fad6e46ff5e51432e51 0.600000000000 1375752 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": 918124, "vin": [ { "gen": { "height": 918114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8866cd6ef23e332e75a2cb0b15f132f8520a2971eccf0fad6e46ff5e51432e51" } } ], "extra": [ 1, 146, 63, 91, 178, 212, 212, 246, 238, 184, 229, 253, 62, 217, 132, 175, 22, 70, 189, 95, 110, 60, 132, 165, 124, 193, 15, 59, 94, 56, 180, 121, 204, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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