← previous blocknext block →recent activity
Analyzing
Block #108,672,372
15 transactions · 12 stateful · 2026-09-28 05:51:21 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,672,372 · 15 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
1w04w19w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49fe70fa…3c13
0x34b655…2a6f
8 touches
6 conflicts
0xfe65bb7b…12d7
0x34b655…2a6f
6 touches
3 conflicts
0xc3baa205…f26e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x6235638c…6436
0x1b6862…e19c
4 touches
1 conflict
0xa17a6243…a41f
0x34b655…2a6f
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x08cc68a2…2a59
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 0x49fe70fa5a…633c13
Audit this contract →
← previous block·next block →recent activity