← previous blocknext block →recent activity
Analyzing
Block #106,042,324
19 transactions · 16 stateful · 2026-09-19 01:10:04 UTC
Parallelism
58/100
Blocked
44%
Avg conflicts / tx
0.74
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,042,324 · 19 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
2w03w14w25w38w49w511w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x60486dba…8d9f
0xd32edf…ff58
5 touches
3 conflicts
0x26253352…1a75
0x34b655…2a6f
4 touches
1 conflict
0x309f47c0…e1cf
0x34b655…2a6f
4 touches
1 conflict
0x3b65c5ca…9f83
0x34b655…2a6f
4 touches
1 conflict
0x48b6f2c7…2ef7
0x34b655…2a6f
4 touches
1 conflict
0x5ad5e6de…e7ad
0x34b655…2a6f
4 touches
1 conflict
0x6d5d1fb5…86a7
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity