← previous blocknext block →recent activity
Analyzing
Block #100,617,955
16 transactions · 12 stateful · 2026-08-31 00:54:01 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,617,955 · 16 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
1w05w16w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb965fed…ee71
0x34b655…2a6f
8 touches
6 conflicts
0x0b05d77e…6f90
0x34b655…2a6f
6 touches
3 conflicts
0x29cd05f5…390c
0x34b655…2a6f
6 touches
3 conflicts
0xffb2bfcf…b92a
0x34b655…2a6f
4 touches
1 conflict
0x044844a0…7418
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x5d4eb697…fd41
0x34b655…2a6f
4 touches
1 conflict
0x7f8107c4…9cb2
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
6 conflicts on slot 0xeb965feda9…c4ee71
Audit this contract →
← previous block·next block →recent activity