Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d18ea271a20a943afa6b2cafa05e7ef828e6f1adde61eaf476e2241730c54b15

Tx prefix hash: e2d925f5837ac39e356f6742347a55de863bdbc85ae0af9ade0488ab9bf1fc2c
Tx public key: 643b5fb95b38da11fd20f1fc05fd2f59bfdfdae6efe6b03bc9772e83b10959e8
Timestamp: 1724767061 Timestamp [UCT]: 2024-08-27 13:57:41 Age [y:d:h:m:s]: 00:220:07:43:32
Block: 1097074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157317 RingCT/type: yes/0
Extra: 01643b5fb95b38da11fd20f1fc05fd2f59bfdfdae6efe6b03bc9772e83b10959e802110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f34919baab52d88214c202ee537103080c8ee775ec6546de4270656c31dfd5da 0.600000000000 1572361 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": 1097084, "vin": [ { "gen": { "height": 1097074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f34919baab52d88214c202ee537103080c8ee775ec6546de4270656c31dfd5da" } } ], "extra": [ 1, 100, 59, 95, 185, 91, 56, 218, 17, 253, 32, 241, 252, 5, 253, 47, 89, 191, 223, 218, 230, 239, 230, 176, 59, 201, 119, 46, 131, 177, 9, 89, 232, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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