← previous blocknext block →recent activity
Analyzing
Block #102,058,253
23 transactions · 21 stateful · 2026-09-05 01:46:59 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,058,253 · 23 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
1w02w16w011w012w116w117w018w219w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x01315072…0e2d
0x34b655…2a6f
4 touches
1 conflict
0x0ffac39e…6d34
0x34b655…2a6f
4 touches
1 conflict
0x173b64af…6c43
0x34b655…2a6f
4 touches
1 conflict
0x25fd5528…ff50
0x34b655…2a6f
4 touches
1 conflict
0x47ea26e4…4386
0x34b655…2a6f
4 touches
1 conflict
0x4f8669e3…de15
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity