Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 993ee16fea85283b4b656e8e220441f7f51dbb8651ee524f23b231819f139c45

Tx prefix hash: 9e78923dee25648aacb3eb3e917c82782535b76dff229e9c823beb0c8b0a4f44
Tx public key: a4b1a0880f9f6d24d517f0376a3d145c9aa495b88278338f8376c19f14f768a7
Timestamp: 1749784079 Timestamp [UCT]: 2025-06-13 03:07:59 Age [y:d:h:m:s]: 00:160:19:21:36
Block: 1303880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112650 RingCT/type: yes/0
Extra: 01a4b1a0880f9f6d24d517f0376a3d145c9aa495b88278338f8376c19f14f768a70211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12bc8c992ed7bf7a634afa87acdc7f44af7daa70598c47331f15f23efec87710 0.600000000000 1791465 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": 1303890, "vin": [ { "gen": { "height": 1303880 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12bc8c992ed7bf7a634afa87acdc7f44af7daa70598c47331f15f23efec87710" } } ], "extra": [ 1, 164, 177, 160, 136, 15, 159, 109, 36, 213, 23, 240, 55, 106, 61, 20, 92, 154, 164, 149, 184, 130, 120, 51, 143, 131, 118, 193, 159, 20, 247, 104, 167, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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