← previous blocknext block →recent activity
Analyzing
Block #117,389,747
10 transactions · 10 stateful · 2026-10-28 17:47:50 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #117,389,747 · 10 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
3w04w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c989dc1…a3e8
0x34b655…2a6f
4 touches
1 conflict
0xe796f8b7…ad55
0x34b655…2a6f
4 touches
1 conflict
0xf9f8a78a…25f3
0x34b655…2a6f
4 touches
1 conflict
0x0667a366…00ce
0x34b655…2a6f
2 touches
0 conflicts
0x19429274…6461
0x34b655…2a6f
2 touches
0 conflicts
0x1be38c4b…3a68
0x34b655…2a6f
2 touches
0 conflicts
0x2902912b…448c
0x34b655…2a6f
2 touches
0 conflicts
0x423ad46a…b3b9
0x34b655…2a6f
2 touches
0 conflicts
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 0x7c989dc111…55a3e8
Audit this contract →
← previous block·next block →recent activity