Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7d4080755670b7b0515e9d539a0bf36cf3ecf61e461771b65b1ca726e01e1e8

Tx prefix hash: 4f9ff45e3cd939c4e0512362029e44a5653f34b9f7feeb7c6e62566953a84fe0
Tx public key: a8fd998b8d5ed166fc0790fa2ee6161797a44145a0d105470afe0818c99d36e0
Timestamp: 1715060085 Timestamp [UCT]: 2024-05-07 05:34:45 Age [y:d:h:m:s]: 00:335:06:04:39
Block: 1016604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239638 RingCT/type: yes/0
Extra: 01a8fd998b8d5ed166fc0790fa2ee6161797a44145a0d105470afe0818c99d36e00211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67e5b60a8db0141c33ea0875acc9a48f207ff73f6b0f032db21ad13d3539ff46 0.600000000000 1480235 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": 1016614, "vin": [ { "gen": { "height": 1016604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67e5b60a8db0141c33ea0875acc9a48f207ff73f6b0f032db21ad13d3539ff46" } } ], "extra": [ 1, 168, 253, 153, 139, 141, 94, 209, 102, 252, 7, 144, 250, 46, 230, 22, 23, 151, 164, 65, 69, 160, 209, 5, 71, 10, 254, 8, 24, 201, 157, 54, 224, 2, 17, 0, 0, 0, 3, 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