Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e606d571e7bb9e3636a3d13804c0823ddd2ecfbf643d196af0a1f72db8e50ff9

Tx prefix hash: 4ff878ed57022aa0e6cd8d2be243ab1006563ef2d60da9a0916cc1a0cbd7b329
Tx public key: 03d696cbc3f56d95821f5c06c9bdd61066455b84e71bb51219e66314ca12a1a2
Timestamp: 1758548241 Timestamp [UCT]: 2025-09-22 13:37:21 Age [y:d:h:m:s]: 00:055:05:01:04
Block: 1374029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39532 RingCT/type: yes/0
Extra: 0103d696cbc3f56d95821f5c06c9bdd61066455b84e71bb51219e66314ca12a1a2021100000004ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5a991934133ec6dcdc65b29466c614ebb581b8743f99d91dab627dc616fac44 0.600000000000 1862114 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": 1374039, "vin": [ { "gen": { "height": 1374029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5a991934133ec6dcdc65b29466c614ebb581b8743f99d91dab627dc616fac44" } } ], "extra": [ 1, 3, 214, 150, 203, 195, 245, 109, 149, 130, 31, 92, 6, 201, 189, 214, 16, 102, 69, 91, 132, 231, 27, 181, 18, 25, 230, 99, 20, 202, 18, 161, 162, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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