← previous blocknext block →recent activity
Analyzing
Block #103,223,534
23 transactions · 19 stateful · 2026-09-09 03:56:40 UTC
Parallelism
70/100
Blocked
42%
Avg conflicts / tx
0.96
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #103,223,534 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w17w28w39w414w116w517w622w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xfa09be5a…1e79
0x34b655…2a6f
8 touches
6 conflicts
0xe7b22aa8…e068
0x34b655…2a6f
8 touches
6 conflicts
0x24b08f9c…e594
0x34b655…2a6f
6 touches
3 conflicts
0x359866c7…de7b
0x34b655…2a6f
6 touches
3 conflicts
0x752d9ee0…e490
0x34b655…2a6f
4 touches
1 conflict
0x754bbcbe…427e
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity