← previous blocknext block →recent activity
Analyzing
Block #102,640,404
19 transactions · 19 stateful · 2026-09-07 02:56:59 UTC
Parallelism
89/100
Blocked
26%
Avg conflicts / tx
0.32
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,640,404 · 19 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
1w02w15w07w110w011w113w014w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ffac39e…6d34
0x34b655…2a6f
4 touches
1 conflict
0x19932f5a…1501
0x34b655…2a6f
4 touches
1 conflict
0x1f3cea1e…9cd5
0x34b655…2a6f
4 touches
1 conflict
0x32e1d03e…68a7
0x34b655…2a6f
4 touches
1 conflict
0x49299fcf…c552
0x34b655…2a6f
4 touches
1 conflict
0x53f315d3…6add
0x34b655…2a6f
4 touches
1 conflict
0x5da92df7…74b5
0x34b655…2a6f
4 touches
1 conflict
0x65f011a5…bc6e
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
1 conflict on slot 0x0ffac39e72…c16d34
Audit this contract →
← previous block·next block →recent activity