Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 722e6ccd59112840d1f8f4b22d16fa1eee27680ee62b16c318e4faba38ea36ac

Tx prefix hash: 4bfae2f9923be5a20e3def925204d9777dbd557ef748c10459d21cf8093aad30
Tx public key: 86d5c6f1d0bbeed23a64ccac7bdfc8aba5473962b2fa0aa3d0541795d5d73f7f
Timestamp: 1752425665 Timestamp [UCT]: 2025-07-13 16:54:25 Age [y:d:h:m:s]: 00:173:14:49:26
Block: 1324733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122876 RingCT/type: yes/0
Extra: 0186d5c6f1d0bbeed23a64ccac7bdfc8aba5473962b2fa0aa3d0541795d5d73f7f0211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fc4d16c241f7aa6ef849ed4dbcedeac2a73bdea3a6a428de7d353c2161f300e 0.600000000000 1812476 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": 1324743, "vin": [ { "gen": { "height": 1324733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fc4d16c241f7aa6ef849ed4dbcedeac2a73bdea3a6a428de7d353c2161f300e" } } ], "extra": [ 1, 134, 213, 198, 241, 208, 187, 238, 210, 58, 100, 204, 172, 123, 223, 200, 171, 165, 71, 57, 98, 178, 250, 10, 163, 208, 84, 23, 149, 213, 215, 63, 127, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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