Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee2cd291ce3c2a81b490fcbf7d503cce507e9705e19c93d07c4e7efaa8c57992

Tx prefix hash: 99d56260bb17c7bca9c69cbffd5174e769c1524ecf05f93165b4b63e28592a79
Tx public key: 48cd2cd2ad35c8d4cd35730c47c8430e4be705ff5e50a0579e0295d1f1a69e39
Timestamp: 1707825188 Timestamp [UCT]: 2024-02-13 11:53:08 Age [y:d:h:m:s]: 00:285:17:24:28
Block: 956622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204557 RingCT/type: yes/0
Extra: 0148cd2cd2ad35c8d4cd35730c47c8430e4be705ff5e50a0579e0295d1f1a69e390211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcb1d54c4b231e1bce369c620e4dc381b99da49aa0db951448365d0969c958a8 0.600000000000 1415930 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": 956632, "vin": [ { "gen": { "height": 956622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcb1d54c4b231e1bce369c620e4dc381b99da49aa0db951448365d0969c958a8" } } ], "extra": [ 1, 72, 205, 44, 210, 173, 53, 200, 212, 205, 53, 115, 12, 71, 200, 67, 14, 75, 231, 5, 255, 94, 80, 160, 87, 158, 2, 149, 209, 241, 166, 158, 57, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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