← previous blocknext block →recent activity
Analyzing
Block #100,925,024
13 transactions · 10 stateful · 2026-09-01 02:39:04 UTC
Parallelism
85/100
Blocked
30%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,925,024 · 13 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
3w05w08w19w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x315e07b8…9823
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x6f0befc9…48e9
0x34b655…2a6f
4 touches
1 conflict
0x6fbc2e5a…e69c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x31ce4179…7928
0x065c9d…c394
4 touches
1 conflict
0x63751385…326d
0x065c9d…c394
4 touches
1 conflict
0x22e0cc1d…ad0d
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
1 conflict on slot 0x315e07b806…529823
Audit this contract →
← previous block·next block →recent activity