Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f22a748057fb55d6aa3dbf35f638924e1eb17b4b9d5fab9bad982336b68b784f

Tx prefix hash: 425b8c39135b48068e28202524c3029effb3cdb074ac0ba1dd831a4d79aee8ff
Tx public key: 2bf20eba06eaede288020b71fb4b4935621815394cf714d624c9f58b60d5cd0a
Timestamp: 1759294312 Timestamp [UCT]: 2025-10-01 04:51:52 Age [y:d:h:m:s]: 00:098:05:48:13
Block: 1380205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70349 RingCT/type: yes/0
Extra: 012bf20eba06eaede288020b71fb4b4935621815394cf714d624c9f58b60d5cd0a021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e9a776e035c7ed73383fcffee1c1a554b5af264cbf81abe3b29b0e730476ab9 0.600000000000 1868316 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": 1380215, "vin": [ { "gen": { "height": 1380205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e9a776e035c7ed73383fcffee1c1a554b5af264cbf81abe3b29b0e730476ab9" } } ], "extra": [ 1, 43, 242, 14, 186, 6, 234, 237, 226, 136, 2, 11, 113, 251, 75, 73, 53, 98, 24, 21, 57, 76, 247, 20, 214, 36, 201, 245, 139, 96, 213, 205, 10, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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