← previous blocknext block →recent activity
Analyzing
Block #106,190,139
11 transactions · 11 stateful · 2026-09-19 13:33:57 UTC
Parallelism
82/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,190,139 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w08w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65903ef9…2567
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x559447b0…eb51
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe93fe6d2…cc1f
0x065c9d…c394
4 touches
1 conflict
0xfb7b69c8…e629
0x065c9d…c394
3 touches
1 conflict
0x6305bcb3…486e
0x065c9d…c394
3 touches
1 conflict
0xa605468c…1bfc
0x34ae4d…3fc5
2 touches
0 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
1 conflict on slot 0x65903ef9a0…7d2567
Audit this contract →
← previous block·next block →recent activity