← previous blocknext block →recent activity
Analyzing
Block #102,248,461
18 transactions · 17 stateful · 2026-09-05 17:51:13 UTC
Parallelism
89/100
Blocked
12%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,248,461 · 18 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
9w010w112w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f7214d…8ec6
0x34b655…2a6f
4 touches
1 conflict
0x9210e826…1414
0x34b655…2a6f
4 touches
1 conflict
0xd271493a…6214
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x24c17fb8…45d1
0x34b655…2a6f
2 touches
0 conflicts
0x49c70181…f8b3
0x34b655…2a6f
2 touches
0 conflicts
0x4c9b66e1…e999
0x34b655…2a6f
2 touches
0 conflicts
0x4f3cc09a…2804
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 0x53f7214d0d…cc8ec6
Audit this contract →
← previous block·next block →recent activity