← previous blocknext block →recent activity
Analyzing
Block #106,916,092
21 transactions · 19 stateful · 2026-09-22 02:28:44 UTC
Parallelism
62/100
Blocked
47%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,916,092 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w18w09w110w211w312w413w514w615w718w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6a595bf…3c45
0x34b655…2a6f
16 touches
28 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
16 touches
28 conflicts
0x42522e76…2592
0x34b655…2a6f
16 touches
28 conflicts
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xfcd5e68f…2a12
0x34b655…2a6f
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x8f4e041c…01ae
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
28 conflicts on slot 0xe6a595bf42…d73c45
Audit this contract →
← previous block·next block →recent activity