Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6c8023b8500c3586961abee800f7badbe59a8cb9cfcbb747736917cbf9f2981

Tx prefix hash: aaecc9a57b08c5f7dbc6631a5a9b58f978c58814e9833afc13ab213ee9fbbf31
Tx public key: b527cda4e5230f7b180bbe886082c01ec89e49d9ff42d2fecbd5c4a4c76129d3
Timestamp: 1731414717 Timestamp [UCT]: 2024-11-12 12:31:57 Age [y:d:h:m:s]: 00:011:16:49:04
Block: 1152094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8381 RingCT/type: yes/0
Extra: 01b527cda4e5230f7b180bbe886082c01ec89e49d9ff42d2fecbd5c4a4c76129d30211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de318810ee168c99fedb949d7d2a99c49be354f52d915565f3f71c2991bc6d9e 0.600000000000 1637685 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": 1152104, "vin": [ { "gen": { "height": 1152094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de318810ee168c99fedb949d7d2a99c49be354f52d915565f3f71c2991bc6d9e" } } ], "extra": [ 1, 181, 39, 205, 164, 229, 35, 15, 123, 24, 11, 190, 136, 96, 130, 192, 30, 200, 158, 73, 217, 255, 66, 210, 254, 203, 213, 196, 164, 199, 97, 41, 211, 2, 17, 0, 0, 0, 1, 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