Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1d1c05547da52b0c084d12b959aa33ece7567e4f6648802b05ebb7586d20ec4

Tx prefix hash: 68e636485aadfff12d7a8ced79ccf4da3c8c393a879b6b6abbb3bf14772cdbbc
Tx public key: 5782b65aedb7d9d1b624e5dac94b16b66939fc33a90e5ae742d5dd8cbf8f9ab5
Timestamp: 1719504930 Timestamp [UCT]: 2024-06-27 16:15:30 Age [y:d:h:m:s]: 00:178:14:31:50
Block: 1053444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127854 RingCT/type: yes/0
Extra: 015782b65aedb7d9d1b624e5dac94b16b66939fc33a90e5ae742d5dd8cbf8f9ab50211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1b4297b55339e8736d9d55cb35ac7513cecce14a229e22ca4234c0180fed126 0.600000000000 1523791 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": 1053454, "vin": [ { "gen": { "height": 1053444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1b4297b55339e8736d9d55cb35ac7513cecce14a229e22ca4234c0180fed126" } } ], "extra": [ 1, 87, 130, 182, 90, 237, 183, 217, 209, 182, 36, 229, 218, 201, 75, 22, 182, 105, 57, 252, 51, 169, 14, 90, 231, 66, 213, 221, 140, 191, 143, 154, 181, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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