Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d56d19700839cfe860cb18b80cf69a41c5644e9c8961b14be1b2c68ad27d39d2

Tx prefix hash: 18627920a1ea14d8b72dac153eef30084292cce00984dba02455aaae0fba0619
Tx public key: 3f0c7f6f65a81937e1b463fbad0332fdf39f8a2684caad0917a3b19fd5289ea8
Timestamp: 1736103065 Timestamp [UCT]: 2025-01-05 18:51:05 Age [y:d:h:m:s]: 00:070:17:58:25
Block: 1190919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50364 RingCT/type: yes/0
Extra: 013f0c7f6f65a81937e1b463fbad0332fdf39f8a2684caad0917a3b19fd5289ea802110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53b8f568eb935bc17590e8caf2441b928c839c2bbdf603259be4e6200f1625ba 0.600000000000 1677442 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": 1190929, "vin": [ { "gen": { "height": 1190919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53b8f568eb935bc17590e8caf2441b928c839c2bbdf603259be4e6200f1625ba" } } ], "extra": [ 1, 63, 12, 127, 111, 101, 168, 25, 55, 225, 180, 99, 251, 173, 3, 50, 253, 243, 159, 138, 38, 132, 202, 173, 9, 23, 163, 177, 159, 213, 40, 158, 168, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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