← previous blocknext block →recent activity
Analyzing
Block #100,063,162
14 transactions · 14 stateful · 2026-08-29 02:18:19 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,063,162 · 14 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
8w09w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe3ab4180…f888
0x34b655…2a6f
3 touches
1 conflict
0xe5011882…5c96
0x34b655…2a6f
3 touches
1 conflict
0x543d36c3…efd2
0x06fc25…2f51
2 touches
0 conflicts
0xc30bd583…6cc1
0x06fc25…2f51
2 touches
0 conflicts
0x0502e3d0…b0e8
0x211cc4…e5d2
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 0x261cbea79d…12e35d
Audit this contract →
← previous block·next block →recent activity