Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f463de5e900266be429e46fbd61c841c9c2518eef8d127be571afc592449736

Tx prefix hash: d7eab4e21251d7cce8e6f72c240e902d2bfa20067695391f5c7043b9ea5ca43b
Tx public key: dad3df9ffec7b0f8cb72766e56982a195a93756c680f910f14e1e58a7825ad40
Timestamp: 1729018071 Timestamp [UCT]: 2024-10-15 18:47:51 Age [y:d:h:m:s]: 00:225:23:08:45
Block: 1132327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161312 RingCT/type: yes/0
Extra: 01dad3df9ffec7b0f8cb72766e56982a195a93756c680f910f14e1e58a7825ad4002110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86bce98c13ac165f259d4c0d451f0454be0b6b243cf1b39585e6a96cd169bca4 0.600000000000 1615240 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": 1132337, "vin": [ { "gen": { "height": 1132327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86bce98c13ac165f259d4c0d451f0454be0b6b243cf1b39585e6a96cd169bca4" } } ], "extra": [ 1, 218, 211, 223, 159, 254, 199, 176, 248, 203, 114, 118, 110, 86, 152, 42, 25, 90, 147, 117, 108, 104, 15, 145, 15, 20, 225, 229, 138, 120, 37, 173, 64, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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