← previous blocknext block →recent activity
Analyzing
Block #100,433,062
12 transactions · 11 stateful · 2026-08-30 09:23:47 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,433,062 · 12 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
1w05w06w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26b2ba12…6ab9
0x34b655…2a6f
4 touches
1 conflict
0xbd3735d7…c973
0x34b655…2a6f
4 touches
1 conflict
0x818e1296…f4d7
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x98e3872e…1b9d
0x34b655…2a6f
3 touches
1 conflict
0x6d5d1fb5…86a7
0x34b655…2a6f
2 touches
0 conflicts
0x9a36cb2e…0929
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 0x26b2ba12bd…a66ab9
Audit this contract →
← previous block·next block →recent activity