← previous blocknext block →recent activity
Analyzing
Block #107,813,317
31 transactions · 24 stateful · 2026-09-25 05:47:15 UTC
Parallelism
84/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,813,317 · 31 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w013w115w016w117w218w219w320w425w026w129w030w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xba522812…1f1f
0x34b655…2a6f
6 touches
3 conflicts
0xd95ed05c…acca
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x2b76a1fb…fdfc
0x34b655…2a6f
6 touches
3 conflicts
0x9ca6fa7b…aeb3
0x34b655…2a6f
4 touches
1 conflict
0xa0cbbfcc…3133
0x34b655…2a6f
4 touches
1 conflict
0xb1bc7bc9…3c43
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
3 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity