← previous blocknext block →recent activity
Analyzing
Block #101,854,243
16 transactions · 15 stateful · 2026-09-04 08:34:10 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,854,243 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf1fdb29b…ee1b
0x34b655…2a6f
4 touches
1 conflict
0x27c8497b…dcc4
0x754704…b603
4 touches
1 conflict
0xbb95fb3e…c47b
0x754704…b603
4 touches
1 conflict
0xf4d134b9…d866
0x754704…b603
4 touches
1 conflict
0x1a489fe9…adcd
0x99c7a7…8bf0
4 touches
1 conflict
0xc48bb6d2…c376
0x99c7a7…8bf0
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
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity