← previous blocknext block →recent activity
Analyzing
Block #102,043,490
19 transactions · 17 stateful · 2026-09-05 00:32:13 UTC
Parallelism
84/100
Blocked
24%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,043,490 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w013w014w115w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x024b482b…16b0
0x34b655…2a6f
4 touches
1 conflict
0x1a2e73cf…5ff5
0x34b655…2a6f
4 touches
1 conflict
0x30c777f3…bacc
0x34b655…2a6f
4 touches
1 conflict
0x65f011a5…bc6e
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x839c0c71…bada
0x34b655…2a6f
4 touches
1 conflict
0x897879a1…9c78
0x34b655…2a6f
4 touches
1 conflict
0x8b5701ab…8f5f
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 0x024b482b0a…2616b0
Audit this contract →
← previous block·next block →recent activity