Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 703dc0731aa7ee31335bc790369ea1a0fea787976df8dfba2c829089c7d1c6ba

Tx prefix hash: 69fa1b39fbed4d81e4cdfae7a2af5f676af3cb2f5763015ae19e3c89a3c820c1
Tx public key: 9bb17abda820de64b1e45f90ca255cbf665d46be452454bf453f8827b9aa8fae
Timestamp: 1765700270 Timestamp [UCT]: 2025-12-14 08:17:50 Age [y:d:h:m:s]: 00:025:09:09:52
Block: 1433294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18185 RingCT/type: yes/0
Extra: 019bb17abda820de64b1e45f90ca255cbf665d46be452454bf453f8827b9aa8fae02110000000370609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf70b2fb2f1831de8e2459a1bbfa76f29625b0ab545c1fa21df9ff76a9e33d2d 0.600000000000 1922073 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": 1433304, "vin": [ { "gen": { "height": 1433294 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf70b2fb2f1831de8e2459a1bbfa76f29625b0ab545c1fa21df9ff76a9e33d2d" } } ], "extra": [ 1, 155, 177, 122, 189, 168, 32, 222, 100, 177, 228, 95, 144, 202, 37, 92, 191, 102, 93, 70, 190, 69, 36, 84, 191, 69, 63, 136, 39, 185, 170, 143, 174, 2, 17, 0, 0, 0, 3, 112, 96, 157, 3, 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