Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e662d2a181fa8f16218374455f0e4f217dfd9bc21ebc2221470e38e58099cad9

Tx prefix hash: 698fb2cbfa43467b618103ff08d5f8b38d16c803810536d9014f5ddad73737dd
Tx public key: 1c83c7318f613ba16f0c084c205984ea448dea52aa0d5c00452a47ef5e945b92
Timestamp: 1711622620 Timestamp [UCT]: 2024-03-28 10:43:40 Age [y:d:h:m:s]: 01:013:12:02:04
Block: 988117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270601 RingCT/type: yes/0
Extra: 011c83c7318f613ba16f0c084c205984ea448dea52aa0d5c00452a47ef5e945b9202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbf83507aa0949567b6f696dd54907339dea8ae3b98b9ea6679525936c1401cb 0.600000000000 1448384 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": 988127, "vin": [ { "gen": { "height": 988117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbf83507aa0949567b6f696dd54907339dea8ae3b98b9ea6679525936c1401cb" } } ], "extra": [ 1, 28, 131, 199, 49, 143, 97, 59, 161, 111, 12, 8, 76, 32, 89, 132, 234, 68, 141, 234, 82, 170, 13, 92, 0, 69, 42, 71, 239, 94, 148, 91, 146, 2, 17, 0, 0, 0, 4, 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