← previous blocknext block →recent activity
Analyzing
Block #102,019,310
18 transactions · 18 stateful · 2026-09-04 22:29:47 UTC
Parallelism
78/100
Blocked
28%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,019,310 · 18 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
4w05w16w07w08w110w211w314w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x75a69dd9…8f57
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x65903ef9…2567
0x34b655…2a6f
4 touches
1 conflict
0xa23619a7…40e4
0x3bd359…433a
2 touches
0 conflicts
0x27c8497b…dcc4
0x754704…b603
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 0x75a69dd900…318f57
Audit this contract →
← previous block·next block →recent activity