← previous blocknext block →recent activity
Analyzing
Block #106,053,194
28 transactions · 25 stateful · 2026-09-19 02:04:46 UTC
Parallelism
82/100
Blocked
44%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,053,194 · 28 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
2w04w05w16w27w08w19w112w219w220w121w122w225w026w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe5f5aab…21d7
0x34b655…2a6f
6 touches
3 conflicts
0x70f57071…47ca
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x07c47b1c…93c8
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x65903ef9…2567
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
3 conflicts on slot 0xfe5f5aab0c…ba21d7
Audit this contract →
← previous block·next block →recent activity