Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d400c14a898bbe0bb17ae10d2a2167ce92246358b4647d4ea5d62e2348005e07

Tx prefix hash: 8f976c63883c8cf3d2230ebe1bd0f92d0fb629873153bcab102716eda131b19e
Tx public key: c707de25aedb14d5dd6d4ccb0d81a7c337def5a0fea038731468d9a57b69a4a2
Timestamp: 1711922319 Timestamp [UCT]: 2024-03-31 21:58:39 Age [y:d:h:m:s]: 01:277:18:42:29
Block: 990604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457273 RingCT/type: yes/0
Extra: 01c707de25aedb14d5dd6d4ccb0d81a7c337def5a0fea038731468d9a57b69a4a202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4760f9394d6b3241b4cae1e705e08151287d26e7adba537ab21a0bb7cccba46 0.600000000000 1450928 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": 990614, "vin": [ { "gen": { "height": 990604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4760f9394d6b3241b4cae1e705e08151287d26e7adba537ab21a0bb7cccba46" } } ], "extra": [ 1, 199, 7, 222, 37, 174, 219, 20, 213, 221, 109, 76, 203, 13, 129, 167, 195, 55, 222, 245, 160, 254, 160, 56, 115, 20, 104, 217, 165, 123, 105, 164, 162, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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