← previous blocknext block →recent activity
Analyzing
Block #76,104,512
12 transactions · 10 stateful · 2026-05-21 19:06:26 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,104,512 · 12 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x29e9eb68…1647
0x25d593…7777
4 touches
1 conflict
0x00000000…0008
0x185747…efbd
4 touches
1 conflict
0xbc40c3c3…b5e1
0x3bd359…433a
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x18aed20c…48f3
0x000000…012a
2 touches
0 conflicts
0xeda2edc3…91d8
0x000000…012a
2 touches
0 conflicts
0x90edce8a…0ab1
0x065c9d…c394
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
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: SPIDERMON (SPIDERMON)
1 conflict on slot 0x29e9eb68cf…061647
Audit this contract →
← previous block·next block →recent activity