← previous blocknext block →recent activity
Analyzing
Block #74,238,291
8 transactions · 8 stateful · 2026-05-13 03:23:00 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,238,291 · 8 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
1w02w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1a7
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a6
0x8d66a4…3095
4 touches
1 conflict
0x74825c4e…32e9
0x8d66a4…3095
4 touches
1 conflict
0x0eac6378…36f4
0x34b655…2a6f
4 touches
1 conflict
0x0178c2de…b37d
0x8d66a4…3095
4 touches
1 conflict
0x00000000…0004
0x8d66a4…3095
4 touches
1 conflict
0x2877f440…c2c8
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 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity