Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bda315ebc6678c3ccbb2c018209724fec1bb1806bea4277eaab994381b02a9f

Tx prefix hash: 97be90fd32a9d5a68ed0d5dc37dbfe4e391c16f79290af97d2b276deff2deea1
Tx public key: 77a7ca1636e1ba12fbbe6fe8b446706f6ac5880348f45d3b9fe374b2d041eb4e
Timestamp: 1712919560 Timestamp [UCT]: 2024-04-12 10:59:20 Age [y:d:h:m:s]: 01:006:03:53:00
Block: 998835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265380 RingCT/type: yes/0
Extra: 0177a7ca1636e1ba12fbbe6fe8b446706f6ac5880348f45d3b9fe374b2d041eb4e02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8309988a49f428371807b67e49fe1084ee4f7addea1083e7dfe2fd453410e3c3 0.600000000000 1459299 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": 998845, "vin": [ { "gen": { "height": 998835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8309988a49f428371807b67e49fe1084ee4f7addea1083e7dfe2fd453410e3c3" } } ], "extra": [ 1, 119, 167, 202, 22, 54, 225, 186, 18, 251, 190, 111, 232, 180, 70, 112, 111, 106, 197, 136, 3, 72, 244, 93, 59, 159, 227, 116, 178, 208, 65, 235, 78, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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