← previous blocknext block →recent activity
Analyzing
Block #102,043,843
23 transactions · 22 stateful · 2026-09-05 00:34:00 UTC
Parallelism
70/100
Blocked
41%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,043,843 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w08w19w210w311w314w416w117w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c6e489e…eb3c
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2c539d94…b63a
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x247cfb80…cca8
0x34b655…2a6f
6 touches
3 conflicts
0x839c0c71…bada
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0x8c6e489e8b…b7eb3c
Audit this contract →
← previous block·next block →recent activity