Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06bb2983a2f9637369a82552a1d93f27280247c3a73487f22d659b1ef26b79dd

Tx prefix hash: 0770568ca1fed4f213b5f930ee18fdf2af1fcadb792c9290d2b6be964d259276
Tx public key: f3ea230d91527c1f3aa5ec415b53675695016b3739fa2f432518411313e8fdc1
Timestamp: 1731771866 Timestamp [UCT]: 2024-11-16 15:44:26 Age [y:d:h:m:s]: 00:166:20:53:49
Block: 1155044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119110 RingCT/type: yes/0
Extra: 01f3ea230d91527c1f3aa5ec415b53675695016b3739fa2f432518411313e8fdc10211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 011f9a9b7a29c7baa99d7f0a1c9511f0e329b0f1811998028ff22f044579fdfc 0.600000000000 1640657 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": 1155054, "vin": [ { "gen": { "height": 1155044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "011f9a9b7a29c7baa99d7f0a1c9511f0e329b0f1811998028ff22f044579fdfc" } } ], "extra": [ 1, 243, 234, 35, 13, 145, 82, 124, 31, 58, 165, 236, 65, 91, 83, 103, 86, 149, 1, 107, 55, 57, 250, 47, 67, 37, 24, 65, 19, 19, 232, 253, 193, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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