← previous blocknext block →recent activity
Analyzing
Block #105,606,109
19 transactions · 17 stateful · 2026-09-17 12:32:05 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,606,109 · 19 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
1w02w03w14w25w39w010w011w117w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35006f8a…8e7f
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x953517cb…cdec
0x34b655…2a6f
8 touches
6 conflicts
0xb7b16dd0…0426
0x34b655…2a6f
8 touches
6 conflicts
0x93aff2a7…49a9
0x34b655…2a6f
4 touches
1 conflict
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0x2ef66342…e727
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
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 0x35006f8a9c…a18e7f
Audit this contract →
← previous block·next block →recent activity