← previous blocknext block →recent activity
Analyzing
Block #107,824,414
19 transactions · 18 stateful · 2026-09-25 06:43:06 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
0.79
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,824,414 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w17w28w39w410w511w617w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7ba83b5…d0a8
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x757b0543…e087
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x44b34ec4…e444
0x34b655…2a6f
4 touches
1 conflict
0x06e35955…0bdd
0x34b655…2a6f
4 touches
1 conflict
0x00f245ce…1e10
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 0xa7ba83b5e1…e4d0a8
Audit this contract →
← previous block·next block →recent activity