Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f26ed30f149666caa8e27461abfcccff11b61a7989109a9f230c458649ecced2

Tx prefix hash: 83d0f56b0852ddd5108057b411fb0a26483858cbb6ac5c8ea9607ec8a6d3c71b
Tx public key: 7ff54b5acb9d2bf9ea10ecb75d54851ad03fd090c31245438c64a2e4b6ea81c2
Timestamp: 1709368901 Timestamp [UCT]: 2024-03-02 08:41:41 Age [y:d:h:m:s]: 01:046:10:41:13
Block: 969425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294191 RingCT/type: yes/0
Extra: 017ff54b5acb9d2bf9ea10ecb75d54851ad03fd090c31245438c64a2e4b6ea81c202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6a2ad696b69735c8e47676e8a22c84dae75e3367cb306871c6287ed47cf5cfb 0.600000000000 1429254 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": 969435, "vin": [ { "gen": { "height": 969425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6a2ad696b69735c8e47676e8a22c84dae75e3367cb306871c6287ed47cf5cfb" } } ], "extra": [ 1, 127, 245, 75, 90, 203, 157, 43, 249, 234, 16, 236, 183, 93, 84, 133, 26, 208, 63, 208, 144, 195, 18, 69, 67, 140, 100, 162, 228, 182, 234, 129, 194, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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