← previous blocknext block →recent activity
Analyzing
Block #104,869,003
14 transactions · 13 stateful · 2026-09-14 22:42:16 UTC
Parallelism
64/100
Blocked
54%
Avg conflicts / tx
1.07
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,869,003 · 14 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
1w02w13w04w15w29w010w311w412w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9722304…6ed0
0x34b655…2a6f
10 touches
10 conflicts
0x7c49736b…3418
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x424e9119…2032
0x34b655…2a6f
6 touches
3 conflicts
0xfe2577ac…677b
0x34b655…2a6f
6 touches
3 conflicts
0x17a7f697…dcb5
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
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
10 conflicts on slot 0xd97223041d…366ed0
Audit this contract →
← previous block·next block →recent activity