Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd67e79fec7c3ba6059fda6ef395ef6d9c4c8335bbb1576db4257454eb31094a

Tx prefix hash: 546fab16c35f61bca6dacd7faed31a317be003693cf1e9119a5f7cd9a9b0c28d
Tx public key: e5f7582379dafb882f512759c45ea56b770650b8f2808680f90eaa71546294e1
Timestamp: 1766178721 Timestamp [UCT]: 2025-12-19 21:12:01 Age [y:d:h:m:s]: 00:014:17:32:50
Block: 1437270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10547 RingCT/type: yes/0
Extra: 01e5f7582379dafb882f512759c45ea56b770650b8f2808680f90eaa71546294e102110000000470609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c48be9c3b1dc8fc4aea86a5097301e7243b0e14cebcc25c62caaa6ec1c89e0c1 0.600000000000 1926077 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": 1437280, "vin": [ { "gen": { "height": 1437270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c48be9c3b1dc8fc4aea86a5097301e7243b0e14cebcc25c62caaa6ec1c89e0c1" } } ], "extra": [ 1, 229, 247, 88, 35, 121, 218, 251, 136, 47, 81, 39, 89, 196, 94, 165, 107, 119, 6, 80, 184, 242, 128, 134, 128, 249, 14, 170, 113, 84, 98, 148, 225, 2, 17, 0, 0, 0, 4, 112, 96, 157, 3, 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