Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5c914c2534a887227a09c7944a115eae5696d49f3fe84bc88c8ba63ae903764

Tx prefix hash: 84c52d0f080544f63a27f081df3769dd376831d8922e2c74820013c1b5013e6c
Tx public key: f768f48fdeaf3a4dc4c533aa2c9d240605c3879ea8f69676f5962882a4c40bc8
Timestamp: 1700728531 Timestamp [UCT]: 2023-11-23 08:35:31 Age [y:d:h:m:s]: 01:124:00:32:26
Block: 897788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349788 RingCT/type: yes/0
Extra: 01f768f48fdeaf3a4dc4c533aa2c9d240605c3879ea8f69676f5962882a4c40bc802110000000175e3f0e9000000000000000000

1 output(s) for total of 0.650512510000 dcy

stealth address amount amount idx
00: ffaeb4a89381fbe2d0f8597ec55d0b1e07765c7a858e71986eb95c67a9bcf277 0.650512510000 1354183 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": 897798, "vin": [ { "gen": { "height": 897788 } } ], "vout": [ { "amount": 650512510, "target": { "key": "ffaeb4a89381fbe2d0f8597ec55d0b1e07765c7a858e71986eb95c67a9bcf277" } } ], "extra": [ 1, 247, 104, 244, 143, 222, 175, 58, 77, 196, 197, 51, 170, 44, 157, 36, 6, 5, 195, 135, 158, 168, 246, 150, 118, 245, 150, 40, 130, 164, 196, 11, 200, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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