← previous blocknext block →recent activity
Analyzing
Block #106,801,486
16 transactions · 16 stateful · 2026-09-21 16:51:52 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,801,486 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w08w19w010w111w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24b2ba87…21ff
0x34b655…2a6f
8 touches
6 conflicts
0x7f01feb3…85be
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0xac0b4a08…faae
0x34b655…2a6f
6 touches
3 conflicts
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0x7f0725e9…66f7
0x34b655…2a6f
4 touches
1 conflict
0x9a74ca82…17d1
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 0x24b2ba879e…a721ff
Audit this contract →
← previous block·next block →recent activity