Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73e372246409cd3865fbd2392c184c6ca97bb6d99be2c5f0bc259b595812ad19

Tx prefix hash: c8f57cf64b53ebf5491b18863013ae4a4c09470cf32662812a8e4d82161fe5c9
Tx public key: 40b2078bc85f94d18a711acab9d4111c07c10ac150a14d1d1110ee41838dc2fc
Timestamp: 1755592501 Timestamp [UCT]: 2025-08-19 08:35:01 Age [y:d:h:m:s]: 00:092:20:12:29
Block: 1349738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66273 RingCT/type: yes/0
Extra: 0140b2078bc85f94d18a711acab9d4111c07c10ac150a14d1d1110ee41838dc2fc021100000005b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d928ce6aeb60cb292d23122d13f2ab06d7dd9e5a528a8c2ef05ec870936ca3ca 0.600000000000 1837673 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": 1349748, "vin": [ { "gen": { "height": 1349738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d928ce6aeb60cb292d23122d13f2ab06d7dd9e5a528a8c2ef05ec870936ca3ca" } } ], "extra": [ 1, 64, 178, 7, 139, 200, 95, 148, 209, 138, 113, 26, 202, 185, 212, 17, 28, 7, 193, 10, 193, 80, 161, 77, 29, 17, 16, 238, 65, 131, 141, 194, 252, 2, 17, 0, 0, 0, 5, 178, 247, 132, 196, 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