Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd34695c71feb30a031a3c94c01fd6828f52b6426803199c483b78fea99cb6f5

Tx prefix hash: afa7ae41bf31ebfd2f240708842174316642a4de995ca2031aa208fdd5fc429a
Tx public key: 78d5d985b57b45bb44c360126c2f596bf5f6d1ddb5a8d2ec296425fba3d21525
Timestamp: 1752068673 Timestamp [UCT]: 2025-07-09 13:44:33 Age [y:d:h:m:s]: 00:125:21:26:13
Block: 1321973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88500 RingCT/type: yes/0
Extra: 0178d5d985b57b45bb44c360126c2f596bf5f6d1ddb5a8d2ec296425fba3d21525021100000004dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bf1d74b8d3d61c7ebd20e21e0efa25e949b4200018ccc67ac55f4f64e3cedd3 0.600000000000 1809684 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": 1321983, "vin": [ { "gen": { "height": 1321973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bf1d74b8d3d61c7ebd20e21e0efa25e949b4200018ccc67ac55f4f64e3cedd3" } } ], "extra": [ 1, 120, 213, 217, 133, 181, 123, 69, 187, 68, 195, 96, 18, 108, 47, 89, 107, 245, 246, 209, 221, 181, 168, 210, 236, 41, 100, 37, 251, 163, 210, 21, 37, 2, 17, 0, 0, 0, 4, 223, 195, 186, 73, 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