← previous blocknext block →recent activity
Analyzing
Block #100,616,113
14 transactions · 13 stateful · 2026-08-31 00:44:45 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,616,113 · 14 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
4w05w16w29w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0476d77b…a514
0x34b655…2a6f
6 touches
3 conflicts
0x1e168c8b…6945
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xc20f02b1…bcb3
0x34b655…2a6f
4 touches
1 conflict
0x0decd120…cf30
0x34b655…2a6f
2 touches
0 conflicts
0x0ed7cc0b…ee52
0x34b655…2a6f
2 touches
0 conflicts
0x9225bafd…11f9
0x34b655…2a6f
2 touches
0 conflicts
0xa6d40b7f…2969
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 0x0476d77bba…41a514
Audit this contract →
← previous block·next block →recent activity