← previous blocknext block →recent activity
Analyzing
Block #100,876,642
9 transactions · 9 stateful · 2026-08-31 22:35:42 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,876,642 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc5c1743…052c
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x11f2dee3…529f
0x34b655…2a6f
2 touches
0 conflicts
0x4bfdfe91…1ec2
0x34b655…2a6f
2 touches
0 conflicts
0x5e8d1e58…a63b
0x34b655…2a6f
2 touches
0 conflicts
0x60ce2df9…5a39
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
1 conflict on slot 0xbc5c174323…89052c
Audit this contract →
← previous block·next block →recent activity