Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78121839b0ef54c70f1079fe73764ac3f2f53c7632e8b7e57681f3467fc6e95d

Tx prefix hash: 45d23cf13d086d55fdcda3406c27f590533fc790c67707f941066c303288e845
Tx public key: 1d9fee4b6ebd6bbe0842a1ac9792941daa8dfc2d4a0e1b9178d10c6f31bace37
Timestamp: 1724459970 Timestamp [UCT]: 2024-08-24 00:39:30 Age [y:d:h:m:s]: 00:256:07:32:20
Block: 1094546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183054 RingCT/type: yes/0
Extra: 011d9fee4b6ebd6bbe0842a1ac9792941daa8dfc2d4a0e1b9178d10c6f31bace37021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6935be83b08ed0660f1ca0d0ff1a340fec434c229398eefdd1ce643bd4ba04c 0.600000000000 1569663 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": 1094556, "vin": [ { "gen": { "height": 1094546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6935be83b08ed0660f1ca0d0ff1a340fec434c229398eefdd1ce643bd4ba04c" } } ], "extra": [ 1, 29, 159, 238, 75, 110, 189, 107, 190, 8, 66, 161, 172, 151, 146, 148, 29, 170, 141, 252, 45, 74, 14, 27, 145, 120, 209, 12, 111, 49, 186, 206, 55, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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