← previous blocknext block →recent activity
Analyzing
Block #104,193,231
13 transactions · 9 stateful · 2026-09-12 13:36:59 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #104,193,231 · 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
3w04w17w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5666db7d…5dc4
0x34b655…2a6f
4 touches
1 conflict
0x51089ee5…deba
0x34b655…2a6f
4 touches
1 conflict
0x91f679af…6ac5
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x2d02f869…1f83
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 0x5666db7d94…495dc4
Audit this contract →
← previous block·next block →recent activity