Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dda9aa14be5fe662b17b7858cded6dcdec3e43765e4ea92ddc80d64ade55aeaa

Tx prefix hash: 6ce64d3747d892a3563420a684be159fc08801c20c8347fe323ae3cbcff2deb1
Tx public key: 2df7d01a11225bf672f92f2d663685a7b209b193b6888aa7d1dda9fa7633bed7
Timestamp: 1725144118 Timestamp [UCT]: 2024-08-31 22:41:58 Age [y:d:h:m:s]: 01:060:08:59:50
Block: 1100195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301592 RingCT/type: yes/0
Extra: 012df7d01a11225bf672f92f2d663685a7b209b193b6888aa7d1dda9fa7633bed7021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eac66f5ca8bc5c527fb3b0e0c407ae9c6c2a24bb42de1277fc13542450d2de1e 0.600000000000 1576168 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": 1100205, "vin": [ { "gen": { "height": 1100195 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eac66f5ca8bc5c527fb3b0e0c407ae9c6c2a24bb42de1277fc13542450d2de1e" } } ], "extra": [ 1, 45, 247, 208, 26, 17, 34, 91, 246, 114, 249, 47, 45, 102, 54, 133, 167, 178, 9, 177, 147, 182, 136, 138, 167, 209, 221, 169, 250, 118, 51, 190, 215, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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