Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5049b743781916af8d5a74b05ff969ac8c80d6d43a7ed9a17706103a415e356

Tx prefix hash: 8c72633e2fc91952c8c69fed5aa927d228e7bbb8ef4aa352a3702f782be8743b
Tx public key: 0697a671b7df0410a53076a79289a3752ee16e0d229e28750d34de3be3ddc84d
Timestamp: 1745108208 Timestamp [UCT]: 2025-04-20 00:16:48 Age [y:d:h:m:s]: 00:199:21:27:25
Block: 1265211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140552 RingCT/type: yes/0
Extra: 010697a671b7df0410a53076a79289a3752ee16e0d229e28750d34de3be3ddc84d0211000000056c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b209e36400c29dbc7c6b8dcf427148a370ad2b0a3f6534958f30437e48ed3a72 0.600000000000 1752414 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": 1265221, "vin": [ { "gen": { "height": 1265211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b209e36400c29dbc7c6b8dcf427148a370ad2b0a3f6534958f30437e48ed3a72" } } ], "extra": [ 1, 6, 151, 166, 113, 183, 223, 4, 16, 165, 48, 118, 167, 146, 137, 163, 117, 46, 225, 110, 13, 34, 158, 40, 117, 13, 52, 222, 59, 227, 221, 200, 77, 2, 17, 0, 0, 0, 5, 108, 152, 170, 61, 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