Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46643c0325e9fa09e33dfa95792780fd9209be593c37c6de19f3757534df57d3

Tx prefix hash: 2be0bb4ac9e537289c003e5dfd8c2a097a1f7929e659744e4cf02e8c6cb8ad17
Tx public key: b2d6c73007f472af1966b596ed9907d0d016d79ae35dd924bd509d9712a7ac63
Timestamp: 1763401453 Timestamp [UCT]: 2025-11-17 17:44:13 Age [y:d:h:m:s]: 00:047:09:52:27
Block: 1414241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33964 RingCT/type: yes/0
Extra: 01b2d6c73007f472af1966b596ed9907d0d016d79ae35dd924bd509d9712a7ac630211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2eef56ef92d02ef9e5d75b2c4001361388383cf2081869b8c3a05cba4b15ff1 0.600000000000 1902728 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": 1414251, "vin": [ { "gen": { "height": 1414241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2eef56ef92d02ef9e5d75b2c4001361388383cf2081869b8c3a05cba4b15ff1" } } ], "extra": [ 1, 178, 214, 199, 48, 7, 244, 114, 175, 25, 102, 181, 150, 237, 153, 7, 208, 208, 22, 215, 154, 227, 93, 217, 36, 189, 80, 157, 151, 18, 167, 172, 99, 2, 17, 0, 0, 0, 1, 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