← previous blocknext block →recent activity
Analyzing
Block #106,931,398
12 transactions · 11 stateful · 2026-09-22 03:45:46 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,931,398 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w37w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaf89f45…ced6
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xcaeee6b1…56a0
0x34b655…2a6f
6 touches
3 conflicts
0x04994ed2…9032
0x34b655…2a6f
4 touches
1 conflict
0x650f366d…72ef
0x34b655…2a6f
4 touches
1 conflict
0x715eeec8…5664
0x34b655…2a6f
4 touches
1 conflict
0xa9988419…9f45
0x34b655…2a6f
4 touches
1 conflict
0xcc844ab5…4c6d
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
6 conflicts on slot 0xfaf89f4544…89ced6
Audit this contract →
← previous block·next block →recent activity