Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 798ea7e3b19bc074f496d852e0191b2ba25f6d7b6e177ea532c88c7e185f97b2

Tx prefix hash: e6df51ffcb6fef2a2b9ffa21dad0b2e1ab6cad2b3519f71cb2993d81ea3218ed
Tx public key: cb8ed8ec81563f1ca9198dacba1ce9eacc0f2afde3f4f34055440d9f173dcaea
Timestamp: 1751799495 Timestamp [UCT]: 2025-07-06 10:58:15 Age [y:d:h:m:s]: 00:138:00:21:10
Block: 1319886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97027 RingCT/type: yes/0
Extra: 01cb8ed8ec81563f1ca9198dacba1ce9eacc0f2afde3f4f34055440d9f173dcaea02110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f629babd12ad5a65a68d99d4e16376c832838dd743c9223720c5df055d81325 0.600000000000 1807579 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": 1319896, "vin": [ { "gen": { "height": 1319886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f629babd12ad5a65a68d99d4e16376c832838dd743c9223720c5df055d81325" } } ], "extra": [ 1, 203, 142, 216, 236, 129, 86, 63, 28, 169, 25, 141, 172, 186, 28, 233, 234, 204, 15, 42, 253, 227, 244, 243, 64, 85, 68, 13, 159, 23, 61, 202, 234, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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