← previous blocknext block →recent activity
Analyzing
Block #112,231,289
15 transactions · 15 stateful · 2026-10-10 16:34:20 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #112,231,289 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w314w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x7aad02c6…b979
0x34b655…2a6f
8 touches
6 conflicts
0xc3483764…f29d
0x1b6862…e19c
4 touches
1 conflict
0x034d2f50…e4c9
0x34b655…2a6f
4 touches
1 conflict
0x067f26cc…c8d4
0x34b655…2a6f
4 touches
1 conflict
0x36a76bd2…1fb0
0x34b655…2a6f
4 touches
1 conflict
0x58620f29…db5a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0013
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity