← previous blocknext block →recent activity
Analyzing
Block #102,005,574
14 transactions · 12 stateful · 2026-09-04 21:20:17 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,005,574 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7772b49…fc12
0x34b655…2a6f
4 touches
1 conflict
0xe8f860c0…35c9
0x34b655…2a6f
4 touches
1 conflict
0xee109478…a9c1
0x34b655…2a6f
4 touches
1 conflict
0xf5d28bce…c32c
0x34b655…2a6f
4 touches
1 conflict
0x04d4f30d…4dfb
0x34b655…2a6f
4 touches
1 conflict
0x3fb3f2e2…fef3
0x34b655…2a6f
4 touches
1 conflict
0x5746581b…0cb1
0x34b655…2a6f
4 touches
1 conflict
0x6823c28e…594c
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
1 conflict on slot 0xf7772b4910…d2fc12
Audit this contract →
← previous block·next block →recent activity