← previous blocknext block →recent activity
Analyzing
Block #101,492,642
16 transactions · 12 stateful · 2026-09-03 02:15:14 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,492,642 · 16 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
3w04w18w09w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x14cc77c7…69c4
0x34b655…2a6f
2 touches
0 conflicts
0x2d071de0…c86e
0x34b655…2a6f
2 touches
0 conflicts
0x38357a83…33d2
0x34b655…2a6f
2 touches
0 conflicts
0x47e2a668…be99
0x34b655…2a6f
2 touches
0 conflicts
0x5906754f…b584
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity