← previous blocknext block →recent activity
Analyzing
Block #106,190,411
15 transactions · 14 stateful · 2026-09-19 13:35:19 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,190,411 · 15 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
3w04w110w011w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67a56c8b…f955
0x34b655…2a6f
4 touches
1 conflict
0xeddf4d98…27f7
0x34b655…2a6f
4 touches
1 conflict
0xf90c6521…d8f0
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xb935707a…140f
0x34b655…2a6f
4 touches
1 conflict
0x8765edd1…a7d5
0x34b655…2a6f
2 touches
0 conflicts
0x8b7b6c7e…f781
0x34b655…2a6f
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 0x67a56c8b2e…d7f955
Audit this contract →
← previous block·next block →recent activity