← previous blocknext block →recent activity
Analyzing
Block #100,982,895
24 transactions · 23 stateful · 2026-09-01 07:30:09 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,982,895 · 24 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
1w02w15w06w28w19w114w015w217w318w322w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa538600d…3da5
0x851145…3f07
8 touches
6 conflicts
0xc3115d49…bd18
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x1c912a68…3b21
0x2a68ba…90c5
6 touches
3 conflicts
0x4213f1c0…219a
0x2a68ba…90c5
6 touches
3 conflicts
0x191e0467…70e5
0x34b655…2a6f
6 touches
3 conflicts
0xb0b2e0e7…ac3b
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 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: 0x851145ea…9f3f07
6 conflicts on slot 0xa538600de5…683da5
Audit this contract →
← previous block·next block →recent activity