← previous blocknext block →recent activity
Analyzing
Block #101,673,190
24 transactions · 15 stateful · 2026-09-03 17:23:31 UTC
Parallelism
92/100
Blocked
33%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,673,190 · 24 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
2w09w010w112w113w014w118w019w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ac0d391…9acb
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x60f8746d…b3d9
0x34b655…2a6f
4 touches
1 conflict
0x9f103821…2645
0x34b655…2a6f
4 touches
1 conflict
0xb4634dcc…b675
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xcc844ab5…4c6d
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
1 conflict on slot 0x0ac0d391dd…4f9acb
Audit this contract →
← previous block·next block →recent activity