← previous blocknext block →recent activity
Analyzing
Block #101,992,333
18 transactions · 16 stateful · 2026-09-04 20:13:05 UTC
Parallelism
89/100
Blocked
6%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,992,333 · 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
16w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x04d4f30d…4dfb
0x34b655…2a6f
2 touches
0 conflicts
0x5746581b…0cb1
0x34b655…2a6f
2 touches
0 conflicts
0x6823c28e…594c
0x34b655…2a6f
2 touches
0 conflicts
0x7daf6443…fd36
0x34b655…2a6f
2 touches
0 conflicts
0x8bf661cb…bcd2
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