← previous blocknext block →recent activity
Analyzing
Block #102,876,605
22 transactions · 22 stateful · 2026-09-07 22:48:36 UTC
Parallelism
86/100
Blocked
18%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,876,605 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w17w28w09w113w019w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x843b596d…0b18
0x34b655…2a6f
4 touches
1 conflict
0xc3656cd1…8269
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0xe0764edd…8269
0xd32edf…ff58
3 touches
1 conflict
0x58620f29…db5a
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 0x843b596d2f…030b18
Audit this contract →
← previous block·next block →recent activity