← previous blocknext block →recent activity
Analyzing
Block #104,206,287
18 transactions · 18 stateful · 2026-09-12 14:43:30 UTC
Parallelism
83/100
Blocked
28%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,206,287 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w010w114w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc2493d3…6898
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xf32be18c…82f0
0x34b655…2a6f
4 touches
1 conflict
0x1398e9f0…69ac
0x34b655…2a6f
4 touches
1 conflict
0x14f03197…2dba
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
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
3 conflicts on slot 0xfc2493d371…f36898
Audit this contract →
← previous block·next block →recent activity