Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7fff9aa79e34a816bdcf83e7278b1f8a8b39219b4f3515d805db77495dd3517

Tx prefix hash: 683c96be16c392c262fe3220677bc01bfc909c9c48ab0755a09dacf21205e9f3
Tx public key: fc9f744b6b31a89c5cdc938a721c36b89cf142499a89761ac74f5094c3bb3034
Timestamp: 1717426234 Timestamp [UCT]: 2024-06-03 14:50:34 Age [y:d:h:m:s]: 01:014:16:23:43
Block: 1036230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271266 RingCT/type: yes/0
Extra: 01fc9f744b6b31a89c5cdc938a721c36b89cf142499a89761ac74f5094c3bb303402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12811ab0b75bd264e48ca9bfb2c12bb6b57c36d0161f8b9071d78c1e9c420374 0.600000000000 1504755 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": 1036240, "vin": [ { "gen": { "height": 1036230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12811ab0b75bd264e48ca9bfb2c12bb6b57c36d0161f8b9071d78c1e9c420374" } } ], "extra": [ 1, 252, 159, 116, 75, 107, 49, 168, 156, 92, 220, 147, 138, 114, 28, 54, 184, 156, 241, 66, 73, 154, 137, 118, 26, 199, 79, 80, 148, 195, 187, 48, 52, 2, 17, 0, 0, 0, 3, 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