Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d3ba406ca0c719e3317803d701a31a4dc2e7c109112b88bb7dfdefa383a333b

Tx prefix hash: cf4f2050e4cb9eea2f23547dd2d6b23c6d8afcaff286054e01155f524deca1a1
Tx public key: af5f8f2803a13f1a197148a8c36a9ab04315ec7192ff4568d0d62f478a70b8a7
Timestamp: 1752734508 Timestamp [UCT]: 2025-07-17 06:41:48 Age [y:d:h:m:s]: 00:115:09:52:09
Block: 1327244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81248 RingCT/type: yes/0
Extra: 01af5f8f2803a13f1a197148a8c36a9ab04315ec7192ff4568d0d62f478a70b8a702110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f654001ddfa263f5d032be6c6fccfebf5d744625ff62f1c7b7998549d9bcf553 0.600000000000 1814997 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": 1327254, "vin": [ { "gen": { "height": 1327244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f654001ddfa263f5d032be6c6fccfebf5d744625ff62f1c7b7998549d9bcf553" } } ], "extra": [ 1, 175, 95, 143, 40, 3, 161, 63, 26, 25, 113, 72, 168, 195, 106, 154, 176, 67, 21, 236, 113, 146, 255, 69, 104, 208, 214, 47, 71, 138, 112, 184, 167, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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