← previous blocknext block →recent activity
Analyzing
Block #102,060,232
13 transactions · 12 stateful · 2026-09-05 01:57:03 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,060,232 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5dd033b6…34b5
0x34b655…2a6f
4 touches
1 conflict
0x33b7fbba…64de
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2249932e…474a
0x34b655…2a6f
2 touches
0 conflicts
0x24f89727…5f59
0x34b655…2a6f
2 touches
0 conflicts
0x32e1d03e…68a7
0x34b655…2a6f
2 touches
0 conflicts
0x4b9b818c…ee64
0x34b655…2a6f
2 touches
0 conflicts
0x51fc8795…126f
0x34b655…2a6f
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 0x5dd033b6c4…ea34b5
Audit this contract →
← previous block·next block →recent activity