Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f90611393ad8cbbaf10f4b5bc9353e0b59b79fce39320b3226e69b02a9ef0f3b

Tx prefix hash: 2fdfdeae98cb310540f14e68935eaa123412717628278dc9ffe3826cdeee8464
Tx public key: 194fa6adeaae4f4d3952038f8b4eced4a1fd668c99805c36da61d917675d3523
Timestamp: 1734539031 Timestamp [UCT]: 2024-12-18 16:23:51 Age [y:d:h:m:s]: 01:019:13:20:05
Block: 1178009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272397 RingCT/type: yes/0
Extra: 01194fa6adeaae4f4d3952038f8b4eced4a1fd668c99805c36da61d917675d3523021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa41b36d74de73c3d184238e7b6841c2e2e624bf2b44001529e7e72e45d73b48 0.600000000000 1664392 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": 1178019, "vin": [ { "gen": { "height": 1178009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa41b36d74de73c3d184238e7b6841c2e2e624bf2b44001529e7e72e45d73b48" } } ], "extra": [ 1, 25, 79, 166, 173, 234, 174, 79, 77, 57, 82, 3, 143, 139, 78, 206, 212, 161, 253, 102, 140, 153, 128, 92, 54, 218, 97, 217, 23, 103, 93, 53, 35, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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