Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9729504d98ad71dd64a93d8f6e635886ebb8941069bdf4e38ab2b47ca167365a

Tx prefix hash: b027b78a5f5fb5b94a892dfe16ada539724dc3d849c87e567bb78e299587b0f2
Tx public key: b1a992d312b589525b87b2333df32cc4a24de7e8c9123cd5f4d3e5942a168550
Timestamp: 1754781222 Timestamp [UCT]: 2025-08-09 23:13:42 Age [y:d:h:m:s]: 00:015:21:19:03
Block: 1343784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10579 RingCT/type: yes/0
Extra: 01b1a992d312b589525b87b2333df32cc4a24de7e8c9123cd5f4d3e5942a1685500211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70126f869cd5d89a0bea07a8fa73d615c2803f09e5a440274e65b438e79ab87b 0.600000000000 1831625 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": 1343794, "vin": [ { "gen": { "height": 1343784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70126f869cd5d89a0bea07a8fa73d615c2803f09e5a440274e65b438e79ab87b" } } ], "extra": [ 1, 177, 169, 146, 211, 18, 181, 137, 82, 91, 135, 178, 51, 61, 243, 44, 196, 162, 77, 231, 232, 201, 18, 60, 213, 244, 211, 229, 148, 42, 22, 133, 80, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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