← previous blocknext block →recent activity
Analyzing
Block #102,247,254
22 transactions · 19 stateful · 2026-09-05 17:45:06 UTC
Parallelism
82/100
Blocked
37%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,247,254 · 22 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
2w03w14w05w17w012w113w214w015w117w318w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5da92df7…74b5
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xad692d7b…00de
0x34b655…2a6f
6 touches
3 conflicts
0x32e1d03e…68a7
0x34b655…2a6f
4 touches
1 conflict
0x463e1e6b…87b5
0x34b655…2a6f
4 touches
1 conflict
0x4f3cc09a…2804
0x34b655…2a6f
4 touches
1 conflict
0x53e08444…d671
0x34b655…2a6f
4 touches
1 conflict
0x56e0d685…c960
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
6 conflicts on slot 0x5da92df7bf…9274b5
Audit this contract →
← previous block·next block →recent activity