← previous blocknext block →recent activity
Analyzing
Block #75,090,244
10 transactions · 8 stateful · 2026-05-17 02:10:47 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,090,244 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1fc22e1…6cbe
0x5afd3e…7620
4 touches
1 conflict
0xfacdf5b4…5a8d
0x5afd3e…7620
4 touches
1 conflict
0x1cce8118…3312
0x34b655…2a6f
2 touches
0 conflicts
0x20ac0567…c954
0x34b655…2a6f
2 touches
0 conflicts
0x2484cc15…5afc
0x34b655…2a6f
2 touches
0 conflicts
0x2c1a56ba…2061
0x34b655…2a6f
2 touches
0 conflicts
0x404314de…df1a
0x3bd359…433a
2 touches
0 conflicts
0x5d82c9b5…004c
0x3bd359…433a
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Liquidity Book Token (LBT)
1 conflict on slot 0xd1fc22e141…c66cbe
Audit this contract →
← previous block·next block →recent activity