← previous blocknext block →recent activity
Analyzing
Block #100,733,110
16 transactions · 15 stateful · 2026-08-31 10:33:16 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,733,110 · 16 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
3w05w06w110w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc87e767e…4bba
0x34b655…2a6f
4 touches
1 conflict
0x28eed2ad…c4b2
0x34b655…2a6f
4 touches
1 conflict
0x4aa1be9f…e721
0x34b655…2a6f
4 touches
1 conflict
0x54bf3074…cb35
0x34b655…2a6f
4 touches
1 conflict
0x6a3f238e…dca9
0x34b655…2a6f
4 touches
1 conflict
0x76c4467d…ce28
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
1 conflict on slot 0xc87e767e77…974bba
Audit this contract →
← previous block·next block →recent activity