← previous blocknext block →recent activity
Analyzing
Block #102,205,943
18 transactions · 16 stateful · 2026-09-05 14:15:51 UTC
Parallelism
89/100
Blocked
19%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,205,943 · 18 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
1w02w14w013w014w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x113a6203…5dd8
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x515f1f83…63fa
0xa633a8…12d5
3 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
2 touches
0 conflicts
0x07c1664b…ce84
0x34b655…2a6f
2 touches
0 conflicts
0x09714014…1f93
0x34b655…2a6f
2 touches
0 conflicts
0x0ac65333…ea1b
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 0x113a62038a…805dd8
Audit this contract →
← previous block·next block →recent activity