← previous blocknext block →recent activity
Analyzing
Block #106,224,791
13 transactions · 13 stateful · 2026-09-19 16:28:24 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,224,791 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w17w09w110w211w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a8f78e3…166b
0x34b655…2a6f
6 touches
3 conflicts
0xe098738f…9bbe
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0xa3916e32…83b8
0x34b655…2a6f
4 touches
1 conflict
0xd911522b…e960
0x34b655…2a6f
4 touches
1 conflict
0xc3e72796…a3ca
0x34b655…2a6f
4 touches
1 conflict
0xa3d78e5e…bb33
0x34b655…2a6f
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: Perpl
3 conflicts on slot 0x3a8f78e3c1…31166b
Audit this contract →
← previous block·next block →recent activity