Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47dc428df69d26184c8b046bd345695ba8a8be96ff513f7789c34d49f64ab682

Tx prefix hash: 115fd8f659c32ffd45f7e3eade014c859b7db4094b5880d27f0ca3abd33c636e
Tx public key: c3f795d43b2b88c971494e29f8fd1c726599f61ce1dcd82386186f3ed09f0649
Timestamp: 1758392267 Timestamp [UCT]: 2025-09-20 18:17:47 Age [y:d:h:m:s]: 00:109:23:47:55
Block: 1372735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78766 RingCT/type: yes/0
Extra: 01c3f795d43b2b88c971494e29f8fd1c726599f61ce1dcd82386186f3ed09f0649021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 772dbcbb2f2d9ce2c290146acab80febcbbf3652acc7439d36f7690f1bb380d3 0.600000000000 1860820 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": 1372745, "vin": [ { "gen": { "height": 1372735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "772dbcbb2f2d9ce2c290146acab80febcbbf3652acc7439d36f7690f1bb380d3" } } ], "extra": [ 1, 195, 247, 149, 212, 59, 43, 136, 201, 113, 73, 78, 41, 248, 253, 28, 114, 101, 153, 246, 28, 225, 220, 216, 35, 134, 24, 111, 62, 208, 159, 6, 73, 2, 17, 0, 0, 0, 2, 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