← previous blocknext block →recent activity
Analyzing
Block #105,584,184
25 transactions · 21 stateful · 2026-09-17 10:41:42 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,584,184 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w011w012w114w015w016w118w119w220w221w323w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8f18c04…a919
0x34b655…2a6f
6 touches
3 conflicts
0x5b6af007…0f35
0x34b655…2a6f
6 touches
3 conflicts
0x0c63d442…6d6b
0x34b655…2a6f
6 touches
3 conflicts
0xe40a656b…a98c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x09e0690d…6e3d
0xe52b14…7230
4 touches
1 conflict
0x17bbe4f8…08c5
0xe52b14…7230
4 touches
1 conflict
0x3cebc8f1…975c
0xe52b14…7230
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
3 conflicts on slot 0xf8f18c04de…52a919
Audit this contract →
← previous block·next block →recent activity