← previous blocknext block →recent activity
Analyzing
Block #102,313,872
20 transactions · 18 stateful · 2026-09-05 23:22:42 UTC
Parallelism
90/100
Blocked
17%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,313,872 · 20 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
4w05w18w011w012w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x2bc211ff…514d
0xe52b14…7230
3 touches
1 conflict
0x3352ac6f…cfb4
0x34b655…2a6f
2 touches
0 conflicts
0x9ca6fa7b…aeb3
0x34b655…2a6f
2 touches
0 conflicts
0xb245fe36…d765
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity