← previous blocknext block →recent activity
Analyzing
Block #102,054,383
19 transactions · 17 stateful · 2026-09-05 01:27:24 UTC
Parallelism
79/100
Blocked
18%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,054,383 · 19 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
1w02w16w09w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0x045532dd…4b7d
0x34b655…2a6f
8 touches
6 conflicts
0x0c6a407c…2b73
0x34b655…2a6f
6 touches
3 conflicts
0x45082691…dff7
0x34b655…2a6f
6 touches
3 conflicts
0xd2fb0612…5edf
0x34b655…2a6f
6 touches
3 conflicts
0xa5390204…06e7
0x34b655…2a6f
5 touches
3 conflicts
0x01315072…0e2d
0x34b655…2a6f
4 touches
1 conflict
0x67043b0b…97d7
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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity