← previous blocknext block →recent activity
Analyzing
Block #106,408,631
12 transactions · 12 stateful · 2026-09-20 07:53:36 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,408,631 · 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
2w03w14w17w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5e4f0ed…6dd0
0x5be4ee…673f
7 touches
6 conflicts
0xc5e4f0ed…6dde
0x5be4ee…673f
7 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x42102e63…8aa7
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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: 0x5be4ee8b…b7673f
6 conflicts on slot 0xc5e4f0edd7…ae6dd0
Audit this contract →
← previous block·next block →recent activity