Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd41d3a1152d32250294f6cdeb69c8bed42e9ae8c3e98b28cc1ec8667406b44b

Tx prefix hash: fdac664ba228a5b8566d17acf1038f335e817c056f17de1c6436b69e14a08c9c
Tx public key: eb9f0d8ccef8615d4e1e244c665a1029be0d4f9aa892b9957c3e32b670075706
Timestamp: 1736969822 Timestamp [UCT]: 2025-01-15 19:37:02 Age [y:d:h:m:s]: 00:060:15:37:34
Block: 1198089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43146 RingCT/type: yes/0
Extra: 01eb9f0d8ccef8615d4e1e244c665a1029be0d4f9aa892b9957c3e32b6700757060211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 419f7e0c31f30189bab79fd2149e2db649d1255953fd3b4077d5cc8c5a432efc 0.600000000000 1684708 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": 1198099, "vin": [ { "gen": { "height": 1198089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "419f7e0c31f30189bab79fd2149e2db649d1255953fd3b4077d5cc8c5a432efc" } } ], "extra": [ 1, 235, 159, 13, 140, 206, 248, 97, 93, 78, 30, 36, 76, 102, 90, 16, 41, 190, 13, 79, 154, 168, 146, 185, 149, 124, 62, 50, 182, 112, 7, 87, 6, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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