Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d00ac47e3552c734066af397156d8fb865ad46a5649170196ea73c891a4ba217

Tx prefix hash: 84a83544caa1709855ed88d91ae2e3007963042e08d0d7912e35a1f08ceaa027
Tx public key: 1a1965d1a7f317b2f78dc362b7b2b13d7e0980644b24dd51964449ae81783092
Timestamp: 1643262426 Timestamp [UCT]: 2022-01-27 05:47:06 Age [y:d:h:m:s]: 02:331:17:21:46
Block: 426133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 755639 RingCT/type: yes/0
Extra: 011a1965d1a7f317b2f78dc362b7b2b13d7e0980644b24dd51964449ae81783092021100000007db0c7f64000000000000000000

1 output(s) for total of 23.770854213000 dcy

stealth address amount amount idx
00: 4126fe5bb8a631bf57e24a3d4af6db6ffa0e32baf518d8bbea420eaa81ec97e9 23.770854213000 834926 of 0

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": 426143, "vin": [ { "gen": { "height": 426133 } } ], "vout": [ { "amount": 23770854213, "target": { "key": "4126fe5bb8a631bf57e24a3d4af6db6ffa0e32baf518d8bbea420eaa81ec97e9" } } ], "extra": [ 1, 26, 25, 101, 209, 167, 243, 23, 178, 247, 141, 195, 98, 183, 178, 177, 61, 126, 9, 128, 100, 75, 36, 221, 81, 150, 68, 73, 174, 129, 120, 48, 146, 2, 17, 0, 0, 0, 7, 219, 12, 127, 100, 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