← previous blocknext block →recent activity
Analyzing
Block #106,952,728
16 transactions · 15 stateful · 2026-09-22 05:33:08 UTC
Parallelism
56/100
Blocked
60%
Avg conflicts / tx
1.69
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,952,728 · 16 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
2w03w14w05w16w17w29w310w011w412w513w615w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb5a6a2b…e4cb
0x34b655…2a6f
14 touches
21 conflicts
0x70986451…c6bd
0x34b655…2a6f
8 touches
6 conflicts
0x8590b692…b267
0x34b655…2a6f
8 touches
6 conflicts
0x148c2efc…4410
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xba1edffb…323e
0x34b655…2a6f
6 touches
3 conflicts
0x9a3772ab…4c59
0x34b655…2a6f
6 touches
3 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0xfb5a6a2ba0…19e4cb
Audit this contract →
← previous block·next block →recent activity