Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b26f65fdc0e75dfb3abcfe57d786e22b35f358fd5f1ddf2651dbcae2e23e5606

Tx prefix hash: 432ebb6686d36e4a38168e894feea6d62d5237052efe073f6e79fdf7ab1e4dd3
Tx public key: b235579e460ad88b54648df1147aca80cedc488067b15cf3cf4b7cac516b062b
Timestamp: 1763305743 Timestamp [UCT]: 2025-11-16 15:09:03 Age [y:d:h:m:s]: 00:042:04:46:54
Block: 1413445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30225 RingCT/type: yes/0
Extra: 01b235579e460ad88b54648df1147aca80cedc488067b15cf3cf4b7cac516b062b02110000000ed6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4509b3f1a5cb73931596bf97372fdc92fd9a1f7b8505c4a9bb413c7bb67bf598 0.600000000000 1901924 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": 1413455, "vin": [ { "gen": { "height": 1413445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4509b3f1a5cb73931596bf97372fdc92fd9a1f7b8505c4a9bb413c7bb67bf598" } } ], "extra": [ 1, 178, 53, 87, 158, 70, 10, 216, 139, 84, 100, 141, 241, 20, 122, 202, 128, 206, 220, 72, 128, 103, 177, 92, 243, 207, 75, 124, 172, 81, 107, 6, 43, 2, 17, 0, 0, 0, 14, 214, 225, 157, 124, 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