← previous blocknext block →recent activity
Analyzing
Block #116,897,457
13 transactions · 10 stateful · 2026-10-27 00:22:42 UTC
Parallelism
85/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #116,897,457 · 13 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
9w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x45fdd7f2…37a3
0x34b655…2a6f
4 touches
1 conflict
0x45fdd7f2…37a4
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x1eda0b2a…f1b5
0x34b655…2a6f
2 touches
0 conflicts
0x2fcde340…64b9
0x34b655…2a6f
2 touches
0 conflicts
0x4b444978…9ca8
0x34b655…2a6f
2 touches
0 conflicts
0x6e831143…b588
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 0x45fdd7f265…3037a3
Audit this contract →
← previous block·next block →recent activity