← previous blocknext block →recent activity
Analyzing
Block #101,502,713
18 transactions · 16 stateful · 2026-09-03 03:05:54 UTC
Parallelism
72/100
Blocked
31%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,502,713 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w110w211w312w415w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3dc5798b…5c87
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xc032787b…ef6d
0x34b655…2a6f
4 touches
1 conflict
0x08bc072e…611f
0x34b655…2a6f
4 touches
1 conflict
0x5934b407…e058
0x34b655…2a6f
4 touches
1 conflict
0x258fcaf5…2084
0x34b655…2a6f
2 touches
0 conflicts
0x2f358e74…1022
0x34b655…2a6f
2 touches
0 conflicts
0x30395dc8…d463
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
6 conflicts on slot 0x3dc5798bb7…f95c87
Audit this contract →
← previous block·next block →recent activity