← previous blocknext block →recent activity
Analyzing
Block #116,896,582
16 transactions · 16 stateful · 2026-10-27 00:18:18 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #116,896,582 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w29w310w415w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2e8bece…67d9
0x34b655…2a6f
8 touches
6 conflicts
0x9db64d13…fb98
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xf9f8a78a…25f3
0x34b655…2a6f
4 touches
1 conflict
0x6235638c…643a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x944e29d8…4452
0x34b655…2a6f
4 touches
1 conflict
0xcb45d9d6…cb84
0x1b6862…e19c
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 0xc2e8beced0…cb67d9
Audit this contract →
← previous block·next block →recent activity