Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5da449f4728a29081e7155eae23c4c1563fd3d309fa88c31c954cb81ada7e96

Tx prefix hash: 4b6b506c83ec832e09e980176aa0a0a01313f2b3fc84dbf5348c6a960839312c
Tx public key: 60b4e354bba22edd069937c2b973790bf40fe9348e0aea443b79dfa3cc55b818
Timestamp: 1680995337 Timestamp [UCT]: 2023-04-08 23:08:57 Age [y:d:h:m:s]: 02:049:17:49:52
Block: 734481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 557694 RingCT/type: yes/0
Extra: 0160b4e354bba22edd069937c2b973790bf40fe9348e0aea443b79dfa3cc55b818021100000005b3164c24000000000000000000

1 output(s) for total of 2.261308292000 dcy

stealth address amount amount idx
00: 5df9504edd015c651a12e4cbef76573ec50afa92f6e22452fc341c5917fd5eda 2.261308292000 1180694 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": 734491, "vin": [ { "gen": { "height": 734481 } } ], "vout": [ { "amount": 2261308292, "target": { "key": "5df9504edd015c651a12e4cbef76573ec50afa92f6e22452fc341c5917fd5eda" } } ], "extra": [ 1, 96, 180, 227, 84, 187, 162, 46, 221, 6, 153, 55, 194, 185, 115, 121, 11, 244, 15, 233, 52, 142, 10, 234, 68, 59, 121, 223, 163, 204, 85, 184, 24, 2, 17, 0, 0, 0, 5, 179, 22, 76, 36, 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