Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 344994b7e02680f321d5ca20506c369b60725c79b4caa015aa4ad9c2ed25b80a

Tx prefix hash: 91a3f10040beedf5586a0d4f81b777f033139ed6d398498551d976c4b2d3134b
Tx public key: 54603e5684a794963b5f795c78c4d08fad53138e42e7b0ce53200f8f9b3420cf
Timestamp: 1724836947 Timestamp [UCT]: 2024-08-28 09:22:27 Age [y:d:h:m:s]: 00:135:04:00:26
Block: 1097648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96685 RingCT/type: yes/0
Extra: 0154603e5684a794963b5f795c78c4d08fad53138e42e7b0ce53200f8f9b3420cf02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67c8c277b5e658fe2e453164440f7333f1e859bc1bfb3d3a2d7922b2eccc3e4f 0.600000000000 1573085 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": 1097658, "vin": [ { "gen": { "height": 1097648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67c8c277b5e658fe2e453164440f7333f1e859bc1bfb3d3a2d7922b2eccc3e4f" } } ], "extra": [ 1, 84, 96, 62, 86, 132, 167, 148, 150, 59, 95, 121, 92, 120, 196, 208, 143, 173, 83, 19, 142, 66, 231, 176, 206, 83, 32, 15, 143, 155, 52, 32, 207, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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