← previous blocknext block →recent activity
Analyzing
Block #108,646,455
22 transactions · 22 stateful · 2026-09-28 03:40:50 UTC
Parallelism
82/100
Blocked
41%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,646,455 · 22 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
2w03w14w05w18w29w114w015w116w117w218w319w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61889706…fa2b
0x34b655…2a6f
6 touches
3 conflicts
0x2ceed6d8…5785
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x7c3ddfce…2c39
0x34b655…2a6f
6 touches
3 conflicts
0x6f42fec4…4d4a
0x34b655…2a6f
4 touches
1 conflict
0x7462b8f2…6312
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
3 conflicts on slot 0x6188970619…88fa2b
Audit this contract →
← previous block·next block →recent activity