← previous blocknext block →recent activity
Analyzing
Block #101,992,445
19 transactions · 17 stateful · 2026-09-04 20:13:39 UTC
Parallelism
89/100
Blocked
12%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,992,445 · 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
2w03w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee46716c…d788
0x34b655…2a6f
4 touches
1 conflict
0x240838f0…5b9e
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x7e06d07b…36b0
0x34b655…2a6f
4 touches
1 conflict
0xd07b013b…90cb
0x34b655…2a6f
4 touches
1 conflict
0x90da437c…e271
0x34b655…2a6f
2 touches
0 conflicts
0x2d02f869…1f83
0x34b655…2a6f
2 touches
0 conflicts
0x40b41e1f…c91a
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 0xee46716c03…10d788
Audit this contract →
← previous block·next block →recent activity