Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3775e80fc2e3314dce12950845cbc38ae4d2ad71130bafbf0e74a19deea5abd

Tx prefix hash: 91d7f7cd2496426879304b8e5af3d231115f428ce81d08f2a86b30bf033f22aa
Tx public key: d5dcee54ad4b48e9dafd03c074b215413bac2a3e27bf52a35b27ed84a24b29e5
Timestamp: 1706231558 Timestamp [UCT]: 2024-01-26 01:12:38 Age [y:d:h:m:s]: 01:143:01:01:41
Block: 943377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363269 RingCT/type: yes/0
Extra: 01d5dcee54ad4b48e9dafd03c074b215413bac2a3e27bf52a35b27ed84a24b29e502110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50f33aa1207dbce89f7544aa88d618dca62828b587619e5e8afe6536ef4395a0 0.600000000000 1401583 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": 943387, "vin": [ { "gen": { "height": 943377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50f33aa1207dbce89f7544aa88d618dca62828b587619e5e8afe6536ef4395a0" } } ], "extra": [ 1, 213, 220, 238, 84, 173, 75, 72, 233, 218, 253, 3, 192, 116, 178, 21, 65, 59, 172, 42, 62, 39, 191, 82, 163, 91, 39, 237, 132, 162, 75, 41, 229, 2, 17, 0, 0, 0, 7, 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