Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71dff512accd96f6c50f38287247ad759d7fd7521d2a96e825b9bf7fff2f043b

Tx prefix hash: 0cec2b8a88ccbda67ad45a5b4f6db7501f9caf5a6ee209cda32044fda3331824
Tx public key: f4086b63255ecbc694f373333838a69ccc6be1e5939d1c7850c05e9089fdd3ce
Timestamp: 1756109279 Timestamp [UCT]: 2025-08-25 08:07:59 Age [y:d:h:m:s]: 00:087:23:38:02
Block: 1353999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62801 RingCT/type: yes/0
Extra: 01f4086b63255ecbc694f373333838a69ccc6be1e5939d1c7850c05e9089fdd3ce0211000000072609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74fc99a1efd43461acaf2986fa951c4f7eca72d64d0c61356b964cf8f8f0fb7d 0.600000000000 1841980 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": 1354009, "vin": [ { "gen": { "height": 1353999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74fc99a1efd43461acaf2986fa951c4f7eca72d64d0c61356b964cf8f8f0fb7d" } } ], "extra": [ 1, 244, 8, 107, 99, 37, 94, 203, 198, 148, 243, 115, 51, 56, 56, 166, 156, 204, 107, 225, 229, 147, 157, 28, 120, 80, 192, 94, 144, 137, 253, 211, 206, 2, 17, 0, 0, 0, 7, 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