Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 644e3ecf5523be721bf864253b8f99e07cac60899d4094c7d5309f5881817f61

Tx prefix hash: f653b75a695d31f9a4d3f670e8936360e91e6132e2f3f1467331feeac0c9b081
Tx public key: a1e133327b85e06f91cbeeb196575166441e6e61bf23e976d93ecd73b2268b7a
Timestamp: 1732890266 Timestamp [UCT]: 2024-11-29 14:24:26 Age [y:d:h:m:s]: 00:121:12:17:24
Block: 1164331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86633 RingCT/type: yes/0
Extra: 01a1e133327b85e06f91cbeeb196575166441e6e61bf23e976d93ecd73b2268b7a0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec21c43b6eb52a4664e7a3360bf4f96d72906339c2e1d75de2fa9e07adf0e254 0.600000000000 1650004 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": 1164341, "vin": [ { "gen": { "height": 1164331 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec21c43b6eb52a4664e7a3360bf4f96d72906339c2e1d75de2fa9e07adf0e254" } } ], "extra": [ 1, 161, 225, 51, 50, 123, 133, 224, 111, 145, 203, 238, 177, 150, 87, 81, 102, 68, 30, 110, 97, 191, 35, 233, 118, 217, 62, 205, 115, 178, 38, 139, 122, 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