← previous blocknext block →recent activity
Analyzing
Block #100,787,411
23 transactions · 22 stateful · 2026-08-31 15:06:35 UTC
Parallelism
91/100
Blocked
18%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,787,411 · 23 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
2w03w04w18w09w113w014w015w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x4a45b318…9716
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3243e72f…1f6d
0x34b655…2a6f
4 touches
1 conflict
0x7975af99…31c7
0x34b655…2a6f
4 touches
1 conflict
0x9ca6fa7b…aeb3
0x34b655…2a6f
4 touches
1 conflict
0xac389ba9…8b45
0x34b655…2a6f
4 touches
1 conflict
0x15c6ded9…48e7
0x754704…b603
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity