← previous blocknext block →recent activity
Analyzing
Block #106,187,230
19 transactions · 18 stateful · 2026-09-19 13:19:19 UTC
Parallelism
74/100
Blocked
56%
Avg conflicts / tx
1.21
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,187,230 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w26w19w112w213w314w315w416w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61f4ba10…5bdf
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
8 touches
6 conflicts
0xbcc075fc…5a83
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x4abfb389…18f4
0x34b655…2a6f
8 touches
6 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
8 touches
6 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
8 touches
6 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
6 conflicts on slot 0x61f4ba1030…d35bdf
Audit this contract →
← previous block·next block →recent activity