Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b5c7d30a738aa35d846e4722ee4630fe6549dec0315477625fb7ebbdb3d361c

Tx prefix hash: bf75266f0c784e23cc226ca730f9321a6091a6cb6383fcdb62cb60b0ee7552bc
Tx public key: fbb869318785e3a7f19f2db7a9f7c2797687b0fcab8379f5fb73757c6a82b14e
Timestamp: 1764141724 Timestamp [UCT]: 2025-11-26 07:22:04 Age [y:d:h:m:s]: 00:000:06:57:32
Block: 1420379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211 RingCT/type: yes/0
Extra: 01fbb869318785e3a7f19f2db7a9f7c2797687b0fcab8379f5fb73757c6a82b14e0211000000044e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c44f8b5bdfc869ed31f88ddd91fff4fd947b637df8107f42d36f09d37a71627c 0.600000000000 1908922 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": 1420389, "vin": [ { "gen": { "height": 1420379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c44f8b5bdfc869ed31f88ddd91fff4fd947b637df8107f42d36f09d37a71627c" } } ], "extra": [ 1, 251, 184, 105, 49, 135, 133, 227, 167, 241, 159, 45, 183, 169, 247, 194, 121, 118, 135, 176, 252, 171, 131, 121, 245, 251, 115, 117, 124, 106, 130, 177, 78, 2, 17, 0, 0, 0, 4, 78, 123, 252, 9, 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