Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d233a313c3f095d46467b4f5d8bd7475300943a728c277ad80a5395f1a36a460

Tx prefix hash: 954cb426a9f965fe435924adab5e0a5a588bf7d0c51ac09bbc9d65c869c5d7e8
Tx public key: 2b623b185a6a33814f3543bbced34591ed3cd28a8d511b0853de6f6c4223b110
Timestamp: 1751845766 Timestamp [UCT]: 2025-07-06 23:49:26 Age [y:d:h:m:s]: 00:131:00:43:25
Block: 1320253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92052 RingCT/type: yes/0
Extra: 012b623b185a6a33814f3543bbced34591ed3cd28a8d511b0853de6f6c4223b11002110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 059e73bd0fdcc25a64b4507b88d4b8a4389d6d6c384a6cf75762e8bc12201d50 0.600000000000 1807950 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": 1320263, "vin": [ { "gen": { "height": 1320253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "059e73bd0fdcc25a64b4507b88d4b8a4389d6d6c384a6cf75762e8bc12201d50" } } ], "extra": [ 1, 43, 98, 59, 24, 90, 106, 51, 129, 79, 53, 67, 187, 206, 211, 69, 145, 237, 60, 210, 138, 141, 81, 27, 8, 83, 222, 111, 108, 66, 35, 177, 16, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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